From: Patrick McHardy <kaber@trash.net>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jeff@garzik.org,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
hadi@cyberus.ca
Subject: Re: [PATCH 2/3] NET: [SCHED] Qdisc changes and sch_rr added for multiqueue
Date: Mon, 18 Jun 2007 23:11:32 +0200 [thread overview]
Message-ID: <4676F504.7090901@trash.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC329030D5A10@orsmsx414.amr.corp.intel.com>
Waskiewicz Jr, Peter P wrote:
>> Nested netlink attributes, like most qdisc use, instead of
>> struct tc_rr_qopt (or additionally). The way you've done it
>> makes it hard to add further attributes later.
>>
>
> I'm going to need to think about this more, since I'm not immediately
> getting what you're referring to. I see the qdisc using tc_prio_qopt as
> a single member; do you have an example outside of the qdiscs I can look
> at and see what you're referring to? Please bear with me: my netlink
> skills are still very green.
>
Qdisc private parameters are within the TCA_OPTION attribute. The
data under that attribute can either be a structure (which you used)
or more netlink attributes specific to a single qdisc, which allows
to easily add new attributes.
For a simple qdisc example look at sch_red or grep for rta_parse_nested
and nla_parse_nested.
>
>> BTw, couldn't you just merge sch_rr with prio? AFAICT you
>> only need a new dequeue function, a new struct Qdisc_ops and
>> a MODULE_ALIAS.
>>
>
> Are you suggesting a module that can determine RR or PRIO at runtime?
> Because the two are so similar, I definitely thought about combining
> them, but because of the dequeue difference, you'd need a load-time
> switch to determine which mode to run the module in. That would break
> ABI for sch_prio, which I was trying to avoid.
Yes, all you need to do is register two different struct Qdisc_ops and
provide an alias for autoloading.
next prev parent reply other threads:[~2007-06-18 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 18:42 [PATCH] NET: Multiple queue hardware support PJ Waskiewicz
2007-06-18 18:42 ` [PATCH 1/3] NET: [DOC] Multiqueue hardware support documentation PJ Waskiewicz
2007-06-18 18:42 ` [PATCH 2/3] NET: [SCHED] Qdisc changes and sch_rr added for multiqueue PJ Waskiewicz
2007-06-18 19:05 ` Patrick McHardy
2007-06-18 20:36 ` Waskiewicz Jr, Peter P
2007-06-18 20:54 ` Patrick McHardy
2007-06-18 21:04 ` Waskiewicz Jr, Peter P
2007-06-18 21:11 ` Patrick McHardy [this message]
2007-06-21 17:55 ` Waskiewicz Jr, Peter P
2007-06-21 18:04 ` Patrick McHardy
2007-06-21 18:12 ` Waskiewicz Jr, Peter P
2007-06-21 18:17 ` Patrick McHardy
2007-06-21 18:23 ` Waskiewicz Jr, Peter P
2007-06-21 19:10 ` Patrick McHardy
2007-06-21 20:15 ` Waskiewicz Jr, Peter P
2007-06-18 18:42 ` [PATCH 3/3] NET: [CORE] Stack changes to add multiqueue hardware support API PJ Waskiewicz
2007-06-18 19:10 ` Patrick McHardy
2007-06-18 20:26 ` Waskiewicz Jr, Peter P
2007-06-18 20:28 ` Patrick McHardy
2007-06-19 6:28 ` David Miller
2007-06-19 17:31 ` Waskiewicz Jr, Peter P
2007-06-19 20:01 ` Waskiewicz Jr, Peter P
2007-06-19 22:37 ` David Miller
2007-06-19 23:11 ` Waskiewicz Jr, Peter P
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=4676F504.7090901@trash.net \
--to=kaber@trash.net \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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;
as well as URLs for NNTP newsgroup(s).