From: Andrew Gallatin <gallatin@myri.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org, ossthema@de.ibm.com
Subject: Re: [PATCH] LRO ack aggregation
Date: Tue, 20 Nov 2007 06:47:57 -0500 [thread overview]
Message-ID: <4742C96D.3050203@myri.com> (raw)
In-Reply-To: <20071119.222214.81458569.davem@davemloft.net>
David Miller wrote:
> From: Herbert Xu <herbert@gondor.apana.org.au>
> Date: Tue, 20 Nov 2007 14:09:18 +0800
>
>> David Miller <davem@davemloft.net> wrote:
>>> Fundamentally, I really don't like this change, it batches to the
>>> point where it begins to erode the natural ACK clocking of TCP, and I
>>> therefore am very likely to revert it before merging to Linus.
>> Perhaps make it a tunable that defaults to off?
>
> That's one idea.
I'd certainly prefer the option to have a tunable to having our
customers see performance regressions when they switch to
the kernel's LRO.
> But if it's there the risk it to have it end up being turned on
> always by distribution vendors, making our off-default pointless
> and the internet gets crapped up with misbehaving Linux TCP
> stacks anyways.
If vendors are going to pick this up, there is the risk of them just
applying this patch (which currently has no tunable to disable it),
leaving their users stuck with it enabled. At least with a tunable,
it would be easy for them to turn it off. And the comments surrounding
it could make it clear why it should default to off.
FWIW, we've seen TCP perform well in a WAN setting using our NICs and
our LRO which does this ack aggregation. For example, the last 2
Supercomputing "Bandwidth Challenges" (making the most of a 10Gb/s
WAN connection) were won by teams using our NICs, with drivers that
did this sort of ack aggregation.
Drew
next prev parent reply other threads:[~2007-11-20 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 15:11 [PATCH] LRO ack aggregation Andrew Gallatin
2007-11-20 5:09 ` David Miller
2007-11-20 6:09 ` Herbert Xu
2007-11-20 6:22 ` David Miller
2007-11-20 11:47 ` Andrew Gallatin [this message]
2007-11-20 11:55 ` David Miller
2007-11-20 13:27 ` Andrew Gallatin
2007-11-20 13:35 ` Evgeniy Polyakov
2007-11-20 13:50 ` Herbert Xu
2007-11-20 14:03 ` Evgeniy Polyakov
2007-11-20 14:08 ` Herbert Xu
2007-11-20 14:37 ` Evgeniy Polyakov
2007-11-21 6:15 ` Bill Fink
2007-11-20 19:45 ` Rick Jones
2007-11-20 22:27 ` David 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=4742C96D.3050203@myri.com \
--to=gallatin@myri.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=ossthema@de.ibm.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).