General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: iccrg@irtf.org, tsvwg@ietf.org, aqm@ietf.org,
	 bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fixes to Linux's network stack in kernels 3.9 and 3.10
Date: Wed, 24 Apr 2013 02:19:56 -0700	[thread overview]
Message-ID: <CAA93jw5vSaKnWoLZ_1bW+kdXORimFOXLew2y=wn5tmqg_1Zisg@mail.gmail.com> (raw)

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

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....


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

             reply	other threads:[~2013-04-24  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  9:19 Dave Taht [this message]
2013-04-24 15:49 ` Eric Dumazet

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='CAA93jw5vSaKnWoLZ_1bW+kdXORimFOXLew2y=wn5tmqg_1Zisg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --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