From: Patrick McHardy <kaber@trash.net>
To: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org,
jeff@garzik.org, auke-jan.h.kok@intel.com
Subject: Re: [PATCH] iproute2: sch_rr support in tc
Date: Thu, 28 Jun 2007 18:40:37 +0200 [thread overview]
Message-ID: <4683E485.8050907@trash.net> (raw)
In-Reply-To: <20070628162158.18762.76713.stgit@localhost.localdomain>
PJ Waskiewicz wrote:
> This patch applies on top of Patrick McHardy's RTNETLINK
> patches to add nested compat attributes. This is needed to maintain
> ABI for sch_{rr|prio} in the kernel with respect to tc. A new option,
> namely multiqueue, was added to sch_prio and sch_rr. This will allow
> a user to turn multiqueue support on for sch_prio or sch_rr at loadtime.
> Also, tc qdisc ls will display whether or not multiqueue is enabled on
> that qdisc. When in multiqueue mode, a user can specify a value of 0 for
> bands, and the number of bands will be created to match the number of
> queues on the device.
>
> This patch is to support the new sch_rr (round-robin) qdisc being proposed
> in NET for multiqueue network device support in the Linux network stack.
> It uses q_prio.c as the template, since the qdiscs are nearly identical,
> outside of the ->dequeue() routine.
>
> Signed-off-by: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> ---
>
> include/linux/pkt_sched.h | 9 +++
> tc/Makefile | 1
> tc/q_prio.c | 24 +++++++--
> tc/q_rr.c | 127 +++++++++++++++++++++++++++++++++++++++++++++
Since rr is not built as a module you could actually put everything
in q_prio and share the code. But I don't really care :)
next prev parent reply other threads:[~2007-06-28 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 16:21 [PATCH] iproute2: sch_rr support in tc PJ Waskiewicz
2007-06-28 16:40 ` Patrick McHardy [this message]
2007-06-28 16:47 ` Waskiewicz Jr, Peter P
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 18:21 PJ Waskiewicz
2007-06-23 21:36 PJ Waskiewicz
2007-06-21 21:26 PJ Waskiewicz
2007-06-18 18:40 PJ Waskiewicz
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=4683E485.8050907@trash.net \
--to=kaber@trash.net \
--cc=auke-jan.h.kok@intel.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@linux-foundation.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).