General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] another sets of leaps forward for linux packet queueing
Date: Sat, 31 Aug 2013 23:15:35 +0200	[thread overview]
Message-ID: <20130831211535.GF15389@sesse.net> (raw)
In-Reply-To: <CAA93jw6ZqyAw5tAywMwTMafyP1qP1GBx_YbocVWbvwm20UF5SQ@mail.gmail.com>

On Sat, Aug 31, 2013 at 01:47:50PM -0700, Dave Taht wrote:
> Eric Dumazet just posted a pure fq scheduler (using the highly optimized
> red/black trees in the kernel)
> 
> http://marc.info/?l=linux-netdev&m=137740009008261&w=2
> 
> which "scales to millions of concurrent flows per qdisc".Jon Corbet wrote
> it up in (subscriber only link) in lwn http://lwn.net/Articles/564978/
> which also details the new tso sizing patch, which fixes the oft complained
> about overlarge tso problem and does much saner things with it....

I think it's hard to overstate the long-term significance of fq and its TCP
pacing; I've done similar things with HTB in the past with excellent results,
so having something non-hackish for this will be awesome. In a few years,
we'll wonder how we ever survived without pacing.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  reply	other threads:[~2013-08-31 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 20:47 Dave Taht
2013-08-31 21:15 ` Steinar H. Gunderson [this message]
2013-09-01  8:03 ` [Bloat] [Codel] " MUSCARIELLO Luca OLNC/OLN
2013-09-01  8:03 ` MUSCARIELLO Luca OLNC/OLN
2013-09-06 15:48 ` 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=20130831211535.GF15389@sesse.net \
    --to=sgunderson@bigfoot.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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