From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: iccrg@irtf.org, tsvwg@ietf.org,
bloat <bloat@lists.bufferbloat.net>,
aqm@ietf.org
Subject: Re: [Bloat] Fixes to Linux's network stack in kernels 3.9 and 3.10
Date: Wed, 24 Apr 2013 08:49:04 -0700 [thread overview]
Message-ID: <1366818544.8964.73.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw5vSaKnWoLZ_1bW+kdXORimFOXLew2y=wn5tmqg_1Zisg@mail.gmail.com>
On Wed, 2013-04-24 at 02:19 -0700, Dave Taht wrote:
> There are a really large string of network related fixes going into
> the next two Linux kernels (3.9 and 3.10), in light of extensive tcp
> and bufferbloat related analyses at google.
>
> Two of the most important (at least to my eye) are:
>
> http://marc.info/?l=linux-netdev&m=136241595507566&w=2
>
> and
>
> http://marc.info/?l=linux-netdev&m=136392337900604&w=2
This one is definitely a must have for people using TSO or GSO
We are experimenting other fixes on this area.
>
> Three more caught my eye as I was poking through the commit histories:
>
> http://marc.info/?l=linux-netdev&m=136382407631873&w=2
>
> http://marc.info/?l=linux-netdev&m=136639199530624&w=2
>
> http://marc.info/?l=linux-netdev&m=136580231922814&w=2
>
> And that's just the tip of the iceberg!
>
> I expect to have to rerun a ton of benchmarks as a result of these
> changes, and to have to throw out a lot of older data. Please plan on
> having to do the same after these kernels are released....
>
>
prev parent reply other threads:[~2013-04-24 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 9:19 Dave Taht
2013-04-24 15:49 ` Eric Dumazet [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1366818544.8964.73.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=iccrg@irtf.org \
--cc=tsvwg@ietf.org \
/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