From: Stephen Hemminger <shemming@brocade.com>
To: Phil Sutter <phil@nwl.cc>
Cc: <netdev@vger.kernel.org>, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [iproute PATCH] man: tc.8: mention Fair Queue scheduler
Date: Mon, 21 Sep 2015 14:30:48 -0700 [thread overview]
Message-ID: <20150921143048.071cea77@urahara> (raw)
In-Reply-To: <1441806068-14585-1-git-send-email-phil@nwl.cc>
On Wed, 9 Sep 2015 15:41:08 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This is rather a placeholder to let users know fq exists at all.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> man/man8/tc.8 | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/man/man8/tc.8 b/man/man8/tc.8
> index feafa05..0081625 100644
> --- a/man/man8/tc.8
> +++ b/man/man8/tc.8
> @@ -151,6 +151,10 @@ The classless qdiscs are:
> Simplest usable qdisc, pure First In, First Out behaviour. Limited in
> packets or in bytes.
> .TP
> +fq
> +Fair Queue Scheduler realises TCP pacing and scales to millions of concurrent
> +flows per qdisc.
> +.TP
> pfifo_fast
> Standard qdisc for 'Advanced Router' enabled kernels. Consists of a three-band
> queue which honors Type of Service flags, as well as the priority that may be
Why just fq?
Why not mention all of the others like codel and fq_codel?
next prev parent reply other threads:[~2015-09-21 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 13:41 [iproute PATCH] man: tc.8: mention Fair Queue scheduler Phil Sutter
2015-09-21 21:30 ` Stephen Hemminger [this message]
2015-09-22 14:18 ` [iproute2 PATCH v2] man: tc.8: mention available qdiscs Phil Sutter
[not found] ` <e5ac64abda5a41a19a9557117dc0f820@HQ1WP-EXMB11.corp.brocade.com>
2015-09-23 23:03 ` Stephen Hemminger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150921143048.071cea77@urahara \
--to=shemming@brocade.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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