NetBSD iscsi.n2net.net 3.99.17 Wasabi NetBSD 3.99.17
(SBLDR_ISCSI_GENERIC-WWM-$Revision: 1.1.4.7 $) #0: Wed Oct 31
18:41:06 UTC
2007 support%wasabisystems.com@localhost i386
I have had decent success w/ the product, but I'm looking for some
sanity
checks and possible pointers to some options for the driver that may
help
put my mind at ease.
Basically, I am seeing input errors on the wm driver:
iscsi# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts
Oerrs
Colls
wm0 1500 <Link> 00:15:17:55:44:b0 85918802 880
51402271 0
0
wm0 1500 fe80::/64 fe80::215:17ff:fe 85918802 880
51402271 0
0
wm0 1500 10.0.2/24 10.0.2.254 85918802 880
51402271 0
0
wm1 1500 <Link> 00:15:17:55:44:b1 124213539 1471
60221587 0
0
wm1 1500 fe80::/64 fe80::215:17ff:fe 124213539 1471
60221587 0
0
wm1 1500 10.0.3/24 10.0.3.254 124213539 1471
60221587 0
0
fxp0 1500 <Link> 00:07:e9:1a:64:57 1280704 0
25223 0
0
fxp0 1500 fe80::/64 fe80::207:e9ff:fe 1280704 0
25223 0
0
fxp0 1500 192.168.2/24 192.168.2.210 1280704 0
25223 0
0
lo0 33192 <Link> 0 0
0 0
0
lo0 33192 127/8 127.0.0.1 0 0
0 0
0
lo0 33192 ::1/128 ::1 0 0
0 0
0
lo0 33192 fe80::/64 fe80::1 0 0
0 0
0
The input error percentage is small.. 0.0011%, but I am trying to
see if I
can do anything to clean it up. Here is what I've done so far:
1. Verified / replaced cabling to the switches (no change)
2. Replaced the switches (no change)
3. Verified that Flow Control is disabled at the Switch level
Any other suggestions on what I should be looking at? What about
Interrupt
Coalescence on the hardware? Under Linux, it's standard practice
that we
disable Interrupt Throttling (at the expense of a little cpu) to
reduce
latency and increase performance across the network, but I'm not
sure how to
accomplish the same thing in a NetBSD environment.
Thanks in advance for any suggestions.