| To: | "'netdev@xxxxxxxxxxx'" <netdev@xxxxxxxxxxx> |
|---|---|
| Subject: | TSO and 2.6.13.2 |
| From: | Ben Greear <greearb@xxxxxxxxxxxxxxx> |
| Date: | Tue, 08 Nov 2005 16:44:05 -0800 |
| Organization: | Candela Technologies |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1 |
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@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] Fix sparse warning in e100 driver., Luiz Fernando Capitulino |
|---|---|
| Next by Date: | RED qdisc not working..., Daniel J Blueman |
| Previous by Thread: | [PATCH] Fix sparse warning in e100 driver., Luiz Fernando Capitulino |
| Next by Thread: | RED qdisc not working..., Daniel J Blueman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |