[EMAIL PROTECTED] wrote:
The problem is tied to TCP/IP, where checks are made to see if either
flag is set, without checking to see if the flag matches the stream.
The partner in crime here is uts/common/ip/tcp/tcp.c:tcp_multisend().
While the IPv4 header flag set on an IPv6 stream is harmless, it just
seems wrong to see it advertised there? The same as fullv4.
What I'm assuming is that the card also supports fullv6 (or else some
TCP transfers over bge would just fail) but that this isn't indicated at
all.
So what's the real problem? Hardware checksum state is on
a per-packet basis. Regardless of the number of open streams
to the driver, packets from different streams end up in the
same tx ring(s), and each tx descriptor has the flag that says
whether or not the NIC should compute the checksum during DMA.
Adi
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
