| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: Current 2.6.x TSO state |
| From: | John Heffner <jheffner@xxxxxxx> |
| Date: | Fri, 1 Oct 2004 16:33:33 -0400 (EDT) |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, <herbert@xxxxxxxxxxxxxxxxxxx> |
| In-reply-to: | <20041001200102.GB23046@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 1 Oct 2004, Andi Kleen wrote: > > As mentioned, the TCP receive buffer auto-tuning takes care > > of all of this in 2.6.6 and later. It's just 2.6.5 doesn't > > have John Heffner's auto-tuning code which is why your test > > case is so stuck in the mud. > > > > Also, the stretch ACK's are quite normal. If the receiver can't > > advertize a larger window, we won't spit out an ACK until > > the ack timeout. > > Ok, but why is the TSO case still slower? Because with TSO enabled, you get bigger back-to-back bursts during which the receiving app can't run. -John |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Current 2.6.x TSO state, David S. Miller |
|---|---|
| Next by Date: | Re: Oops at __neigh_for_each_release (2.6.9-rc3), David S. Miller |
| Previous by Thread: | Re: Current 2.6.x TSO state, David S. Miller |
| Next by Thread: | Re: Current 2.6.x TSO state, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |