From: Stephen Hemminger <stephen@networkplumber.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] qdisc: allow setting default queuing discipline
Date: Wed, 28 Aug 2013 10:28:35 -0700 [thread overview]
Message-ID: <20130828102835.2cfa5d41@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1377710453.8277.11.camel@edumazet-glaptop>
On Wed, 28 Aug 2013 10:20:53 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2013-08-28 at 09:18 -0700, Stephen Hemminger wrote:
>
> > Although your idea adds completeness, not sure if it is worth it.
> > The thing is if user is using HTB, they already are using tc
> > commands to set it up, therefore the additional script steps to choose some
> > other qdisc for the leaf nodes doesn't seem like a burden.
> > Therefore the sysctl doesn't help much and might even create more
> > confusion because there is now two places to update.
>
> Well, I need such a facility because I cannot change HTB setup.
>
> I can boot a new kernel, yet not really change user scripts, especially
> when tc setup is actually not a script, but a complex binary doing
> constant changes in a complex and dynamic HTB hierarchy.
>
>
>
Hate to say it but maybe module parameter to htb would be an alternative
if you have to deal with that.
next prev parent reply other threads:[~2013-08-28 17:28 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
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 [this message]
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=20130828102835.2cfa5d41@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).