netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Rick Jones <rick.jones2@hp.com>
Cc: m.iatrou@freemail.gr, netdev@oss.sgi.com
Subject: Re: e1000 (?) jumbo frames performance issue
Date: Thu, 5 May 2005 14:33:18 -0700	[thread overview]
Message-ID: <20050505143318.004566a9.davem@davemloft.net> (raw)
In-Reply-To: <427A7F5B.8050704@hp.com>

On Thu, 05 May 2005 13:17:31 -0700
Rick Jones <rick.jones2@hp.com> wrote:

> I seem to recall that some of the stack defaults for SO_SNDBUF (IIRC) would 
> result in netperf sending 16KB at a time into the connection - once you sent the 
> MTU above 16K you may have started running into issues with Nagle and delayed 
> ACK?  You could try some tests adding a test-specific -D to disable Nagle, or -C 
> to set TCP_CORK, or use -m to set the send size to say, 32KB.

Yes, for one don't expect reasonable behavior if the MTU is near to or less
than the send buffer size in use.

Also, many of Nagle's notions start to fall apart at such high MTU settings.
For example, all of Nagle (even with Minshall's modifications) basically define
"small packet" as anything smaller than 1 MSS.

So something to look into (besides increasing your send buffer size with jacking
up the MTU so large) is changing Nagle to use some constant.  Perhaps something like
512 bytes or smaller, or even 128 bytes or smaller.

  reply	other threads:[~2005-05-05 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 16:28 e1000 (?) jumbo frames performance issue Michael Iatrou
2005-05-05 20:17 ` Rick Jones
2005-05-05 21:33   ` David S. Miller [this message]
2005-05-05 21:54     ` Rick Jones
2005-05-05 22:17       ` David S. Miller
2005-05-05 23:24         ` Rick Jones
2005-05-05 21:55   ` Michael Iatrou
2005-05-05 22:26     ` Michael Iatrou
2005-05-06 16:18     ` Rick Jones

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=20050505143318.004566a9.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=m.iatrou@freemail.gr \
    --cc=netdev@oss.sgi.com \
    --cc=rick.jones2@hp.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).