netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Andi Kleen <ak@suse.de>
Cc: ak@suse.de, netdev@oss.sgi.com, jheffner@psc.edu,
	herbert@gondor.apana.org.au
Subject: Re: Current 2.6.x TSO state
Date: Fri, 1 Oct 2004 12:56:43 -0700	[thread overview]
Message-ID: <20041001125643.30c6830f.davem@davemloft.net> (raw)
In-Reply-To: <20041001195146.GA23046@wotan.suse.de>

On Fri, 1 Oct 2004 21:51:47 +0200
Andi Kleen <ak@suse.de> wrote:

> > >      max win adv:            5840 bytes     max win adv:           63712 bytes
> > >      min win adv:            5840 bytes     min win adv:            5792 bytes
> > 
> > That stinks that the receiver is only using a 64K window,
> > that's way too small for gigabit.
> 
> Just using the default, no tuning.
> 
> I have some patches in the pipeline to do automatic window tuning
> based on link speed based on dev->features. But they were actually more 
> intended for 10Gbit/s (where all the defaults are completely inadequate)  
> And it needs a bit more work. 

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.

  reply	other threads:[~2004-10-01 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01  4:32 Current 2.6.x TSO state David S. Miller
2004-10-01 10:11 ` Andi Kleen
2004-10-01 19:47   ` David S. Miller
2004-10-01 19:51     ` Andi Kleen
2004-10-01 19:56       ` David S. Miller [this message]
2004-10-01 20:01         ` Andi Kleen
2004-10-01 20:15           ` David S. Miller
2004-10-01 20:33           ` John Heffner
2004-10-01 23:19         ` Andi Kleen
2004-10-02  0:04           ` David S. Miller
2004-10-01 13:06 ` Herbert Xu
2004-10-03 21:50   ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041001125643.30c6830f.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ak@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jheffner@psc.edu \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).