From: Eric Dumazet <eric.dumazet@gmail.com>
To: MUSCARIELLO Luca IMT/OLN <luca.muscariello@orange.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] TSO sizing fixes and the new paced "fq" scheduler in Linux 3.12
Date: Wed, 25 Sep 2013 09:58:33 -0700 [thread overview]
Message-ID: <1380128313.3165.157.camel@edumazet-glaptop> (raw)
In-Reply-To: <5243036F.90302@orange.com>
On Wed, 2013-09-25 at 17:38 +0200, Luca MUSCARIELLO wrote:
> Then, I feel like FQ is a bad name to call this "newFQ".
> It's an implementation of a fair TCP pacer. Which is very useful, but FQ
> is kind of misleading, IMHO.
No problem, feel free to send a patch. I am very bad at choosing names.
next prev parent reply other threads:[~2013-09-25 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 23:18 [Bloat] " Dave Taht
2013-09-24 12:25 ` [Bloat] [aqm] " James Roberts
2013-09-25 15:15 ` Eric Dumazet
2013-09-25 15:38 ` Luca MUSCARIELLO
2013-09-25 16:58 ` Eric Dumazet [this message]
2013-09-29 5:49 ` Dave Taht
2013-09-29 8:02 ` Alex Elsayed
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=1380128313.3165.157.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=luca.muscariello@orange.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