Sent to wrong list first time...
-------- Original Message -------- Subject: TSO and 2.6.13.2 Date: Tue, 08 Nov 2005 16:44:05 -0800 From: Ben Greear <[EMAIL PROTECTED]> Organization: Candela Technologies To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]> It appears that I can (almost?) completedly deadlock a TCP connection when using TSO on 2.6.13.2. My test involves trying to send 200Mbps between two interfaces. With TSO enabled (ie, the default for e1000 NICs), in less than 1 minute, there are no more packets transmitted, though it does run nice and fast untill it completely breaks :P I disabled TSO with ethtool, and now it seems to be working reliably. I can attempt to grab network traces if this is worth pursuing. Considering the ongoing troubles with TSO, it is my opinion that it should be disabled by default...but maybe I'm just unlucky. Thanks, Ben -- Ben Greear <[EMAIL PROTECTED]> Candela Technologies Inc http://www.candelatech.com -- Ben Greear <[EMAIL PROTECTED]> Candela Technologies Inc http://www.candelatech.com - 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
