* TSO and 2.6.13.2
@ 2005-11-09 0:44 Ben Greear
0 siblings, 0 replies; only message in thread
From: Ben Greear @ 2005-11-09 0:44 UTC (permalink / raw)
To: 'netdev@oss.sgi.com'
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 <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-11-09 0:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-09 0:44 TSO and 2.6.13.2 Ben Greear
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).