Environment is 2.6.16.9 with e1000 NICs. Paul and I (as part of the Quagga project) are working on a user mode method for doing BGP MD5 checksums using ip_queue. All is working except when TSO is enabled I am seeing some problems.
It appears that when TSO is enabled, ip_queue can be used to manipulate packets that have a size higher than the particular MSS (and MTU) for a TCP stream. This results in a larger than MSS packet going out to the NIC with a TCP MD5 checksum, getting split by the NIC to match the MTU of the LAN, and then being received as multiple packets with incorrect MD5 checksums. Then a retransmit with a smaller/correct MSS happens and the packets are received with valid MD5 checksums. So in effect, the data eventually makes it across the link, but it is sent twice, once with invalid checksums and once with valid checksums, and throughput is slow. When TSO is disabled, things happen as they should. Does this sound like a bug or by design? Does it make sense that ip_queue mangled packets be subjected to TSO, given that the TCP header can be messed with by the user mode code? Chris - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
