summaryrefslogtreecommitdiffstats
path: root/sys/nfsserver
diff options
context:
space:
mode:
authortruckman <truckman@FreeBSD.org>2003-05-25 05:04:26 +0000
committertruckman <truckman@FreeBSD.org>2003-05-25 05:04:26 +0000
commit52630e2ed7ef26be3e92783583a39f716c3c1149 (patch)
tree3790f532620a89d7cbe6c964cee736171ae5b3f9 /sys/nfsserver
parent8543e9caa04d8d2e799c226daef70c271e054af7 (diff)
downloadFreeBSD-src-52630e2ed7ef26be3e92783583a39f716c3c1149.zip
FreeBSD-src-52630e2ed7ef26be3e92783583a39f716c3c1149.tar.gz
Always set the hardware parse bit in the IPCB structure when this
structure, which is new to the 82550 and 82551, is used to transmit a packet. This appears to fix the packet truncation problem that was observed when using 82550-based fxp cards to transmit ICMP or fragmented UDP packets of certain lengths which only had one to three bytes in the second and final mbuf of the packet. This matches a note in the "Intel 8255x 10/100 Mbps Ethernet Controller Family Open Source Software Developer Manual", which says that the hardware parse bit should be set when sending these types of packets. There have also been unconfirmed reports of similar problems when transmitting TCP packets, which should not be affected by the above mentioned change because the hardware parse bit was already being set if the stack requested hardware checksumming of the packet. If the problem remains, the use of the IPCB structure can be disabled to cause the driver to fall back to using the older 82559 interface with 82550-based cards by setting hint.fxp.UNIT_NUMBER.ipcbxmit_disable to a non-zero value at boot time, or using kenv to set this variable before using kldload to load the fxp driver. Approved by: re (jhb)
Diffstat (limited to 'sys/nfsserver')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud