netdev
[Top] [All Lists]

Re: Current 2.6.x TSO state

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: Current 2.6.x TSO state
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Fri, 1 Oct 2004 17:04:56 -0700
Cc: ak@xxxxxxx, netdev@xxxxxxxxxxx, jheffner@xxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20041001231939.GC23046@xxxxxxxxxxxxx>
References: <20040930213221.06a3f5b3.davem@xxxxxxxxxxxxx> <20041001121123.19511403.ak@xxxxxxx> <20041001124733.1ac4266a.davem@xxxxxxxxxxxxx> <20041001195146.GA23046@xxxxxxxxxxxxx> <20041001125643.30c6830f.davem@xxxxxxxxxxxxx> <20041001231939.GC23046@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Sat, 2 Oct 2004 01:19:39 +0200
Andi Kleen <ak@xxxxxxx> 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
> 
> How do you explain the 2-4MB/s less with manually increased 
> receive buffers? 

Some scheduling differences, I suppose.

Frankly, I've done what I can with the TSO stuff at this point.

All I get from you are "it's slower" and no code, I've had to
write and fix and debug everything for you.  The performance
is close or on-par to non-TSO and more importantly TSO abides
by the congestion window and MSS values properly now.  That's
10 times more important than 2-4MB/s performance difference.

Or maybe I should revert all of the TSO work so that all SpecWEB
submissions done with 2.6.x kernels get invalidated?

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