All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] qdisc: allow setting default queuing discipline
Date: Tue, 27 Aug 2013 16:22:52 -0700	[thread overview]
Message-ID: <521D34CC.205@candelatech.com> (raw)
In-Reply-To: <20130827161908.26062336@nehalam.linuxnetplumber.net>

On 08/27/2013 04:19 PM, Stephen Hemminger wrote:
> By default, the pfifo_fast queue discipline has been used by default
> for all devices. But we have better choices now.
>
> This patch allow setting the default queueing discipline with sysctl.
> This allows easy use of better queueing disciplines on all devices
> without having to use tc qdisc scripts. It is intended to allow
> an easy path for distributions to make fq_codel or sfq the default
> qdisc.
>
> This patch also makes pfifo_fast more of a first class qdisc, since
> it is now possible to manually override the default and explicitly
> use pfifo_fast. The behavior for systems who do not use the sysctl
> is unchanged, they still get pfifo_fast
>
> Also removes leftover random # in sysctl net core.

> +CoDel (codel) or fair queue CoDel (fq_codel). Dont' use queuing disciplines

nit: Don't has typo above....

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2013-08-27 23:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 23:19 [PATCH net-next] qdisc: allow setting default queuing discipline Stephen Hemminger
2013-08-27 23:22 ` Ben Greear [this message]
2013-08-30  2:25   ` David Miller
2013-08-28  4:00 ` Eric Dumazet
2013-08-28  4:57   ` Eric Dumazet
2013-08-28 16:18     ` Stephen Hemminger
2013-08-28 17:20       ` Eric Dumazet
2013-08-28 17:28         ` Stephen Hemminger
2013-08-29 12:02           ` Eric Dumazet
2013-08-30  2:23 ` David Miller

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=521D34CC.205@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.