From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Eric Dumazet <edumazet@google.com>,
tsv-area@ietf.org, bloat <bloat@lists.bufferbloat.net>,
aqm@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [Bloat] Flow queuing performance (was: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt)
Date: Sun, 17 Mar 2013 12:32:40 -0700 [thread overview]
Message-ID: <1363548760.29475.87.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130317122449.3dce3692@nehalam.linuxnetplumber.net>
On Sun, 2013-03-17 at 12:24 -0700, Stephen Hemminger wrote:
> On Sun, 17 Mar 2013 15:12:16 -0400
> Jim Gettys <jg@freedesktop.org> wrote:
>
> > As a result, at the last Linux Plumber's Conference in August, there was
> > general consensus that we could replace PFIFO_FAST as the default qdisc in
> > Linux, awaiting just our confidence that fq_codel (or something very
> > similar) was mature enough for such a step.
>
> The only thing holding this back is that some user's still want to have priority queueing
> of control packets. I (and others) have done some experiments on layering a traditional
> three class priority layer on top of fq_codel, but nothing concrete has been submitted
> for review.
I did a patch on top of fq_codel to add 3 bands (same prio
classification than pfifo_fast).
I added a new attribute at that time to enable this 3 bands (and
disabling the external classifier, as it uses same skb->priority field.)
I probably better clone fq_codel, because if we want a pfifo_fast
replacement, it should run without the help of a "tc" command.
next prev parent reply other threads:[~2013-03-17 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 19:12 Jim Gettys
2013-03-17 19:24 ` Stephen Hemminger
2013-03-17 19:32 ` Eric Dumazet [this message]
2013-03-18 4:30 ` Mikael Abrahamsson
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=1363548760.29475.87.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=edumazet@google.com \
--cc=stephen@networkplumber.org \
--cc=swmike@swm.pp.se \
--cc=tsv-area@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