From: Eric Dumazet <eric.dumazet@gmail.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: [Cerowrt-devel] [Codel] another sets of leaps forward for linux packet queueing
Date: Fri, 06 Sep 2013 08:48:25 -0700 [thread overview]
Message-ID: <1378482505.31445.27.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw6ZqyAw5tAywMwTMafyP1qP1GBx_YbocVWbvwm20UF5SQ@mail.gmail.com>
On Sat, 2013-08-31 at 13:47 -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/
Dav, I saw your message on Facebook
Call me on 415-646-5783
prev parent reply other threads:[~2013-09-06 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 20:47 [Cerowrt-devel] " Dave Taht
2013-09-06 15:48 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378482505.31445.27.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.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