| To: | davem@xxxxxxxxxxxxx (David S. Miller) |
|---|---|
| Subject: | Re: bad TSO performance in 2.6.9-rc2-BK |
| From: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
| Date: | Fri, 24 Sep 2004 09:41:04 +1000 |
| Cc: | ak@xxxxxxx, niv@xxxxxxxxxx, andy.grover@xxxxxxxxx, anton@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040923161141.4ea9be4c.davem@davemloft.net> |
| Organization: | Core |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.4.27-hx-1-686-smp (i686)) |
David S. Miller <davem@xxxxxxxxxxxxx> wrote: > > That means as the window fills up, we have to see 44 ACKs > before we are able to send the next TSO frame. Needless to > say that breaks ACK clocking completely. Hang on a second, the same problem would occur before the congestion changes were made, right? I thought Anton was saying that with the old kernels he was getting 100MB/s with TSO enabled... Anton, can you please get tcpdump to somehow show the length of the TSO packets so that we know what the factor is being set to? Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt |
| Previous by Date: | Re: bad TSO performance in 2.6.9-rc2-BK, David S. Miller |
|---|---|
| Next by Date: | [TCP] Fix tcp_current_mss when MTU changes, Herbert Xu |
| Previous by Thread: | Re: bad TSO performance in 2.6.9-rc2-BK, David S. Miller |
| Next by Thread: | Re: bad TSO performance in 2.6.9-rc2-BK, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |