[Top] [All Lists]

Re: 2.6.10 TCP troubles -- suggested patch

To: Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>
Subject: Re: 2.6.10 TCP troubles -- suggested patch
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Tue, 15 Feb 2005 15:25:04 -0800
Cc: kuznet@xxxxxxxxxxxxx, rick.jones2@xxxxxx, hubert.tonneau@xxxxxxxxxxxxxx, shemminger@xxxxxxxx, romieu@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20050212195246.GA28895@xxxxxxxxxxxxxxx>
References: <0525M9211@xxxxxxxxxxxxxxxxxxxxx> <420D37A3.6020209@xxxxxx> <20050211170958.17fcde21.davem@xxxxxxxxxxxxx> <20050212143105.GB27456@xxxxxxxxxxxxxxx> <20050212112811.13a0b97d.davem@xxxxxxxxxxxxx> <20050212195246.GA28895@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Sat, 12 Feb 2005 22:52:46 +0300
Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx> wrote:

> Exactly. That's why the next test should be with disabled TSO in 2.6.9.
> If too rare PSHs were a problem, it will show as the same disaster there.
> [ And, to be honest, in this case, I daresay MacOS X may be left with its bugs
>   alone. Or we could help it with something like setting PSH when we are in 
> slow
>   start and each half of CWND after completion of slow start. Or just set
>   PSH on each frame. ]

Setting it every other frame would fix the problem, just forcing it to
miss header prediction path is what is needed to avoid the silly delayed
ACK behavior.  And PSH is one way to do that.

<Prev in Thread] Current Thread [Next in Thread>