From: Patrick McHardy <kaber@trash.net>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: Adrian Bunk <bunk@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: [2.6 patch] remove CONFIG_NET_SCH_RR
Date: Mon, 23 Jun 2008 21:18:35 +0200 [thread overview]
Message-ID: <485FF70B.6010001@trash.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC3290549C885@orsmsx414.amr.corp.intel.com>
Waskiewicz Jr, Peter P wrote:
>> Commit d62733c8e437fdb58325617c4b3331769ba82d70
>> ([SCHED]: Qdisc changes and sch_rr added for multiqueue)
>> added a NET_SCH_RR option that was unused since the code
>> went unconditionally into sch_prio.
>
> I don't agree we should remove this option, purely for the fact that
> there isn't any way a user would know the qdisc existed without reading
> the code. I'd rather see a change to sch_prio.c to correctly wrap the
> RR code, which I should have done in the first place. My hurdle is when
> the module is selected, NET_SCH_RR isn't defined to be used as an #ifdef
> check in the code. Only when it's selected to be built-in is the symbol
> defined. If I can get around that, I'll generate a patch to properly
> wrap sch_prio.c code. I know I'm missing something silly, so any
> guidance is appreciated.
For modular selected options, the name is <name>_MODULE (so
CONFIG_NET_SCH_RR_MODULE in this case).
I tend to agree with Adrian though, this option doesn't
provide any value.
next prev parent reply other threads:[~2008-06-23 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 17:47 [2.6 patch] remove CONFIG_NET_SCH_RR Adrian Bunk
2008-06-23 18:31 ` Waskiewicz Jr, Peter P
2008-06-23 19:18 ` Patrick McHardy [this message]
2008-06-23 19:40 ` Adrian Bunk
2008-06-23 19:59 ` Waskiewicz Jr, Peter P
2008-06-23 21:52 ` David Miller
2008-06-28 2:54 ` 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=485FF70B.6010001@trash.net \
--to=kaber@trash.net \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rpjday@crashcourse.ca \
/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).