From: jamal <hadi@cyberus.ca>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: davem@davemloft.net, jarkao2@gmail.com, shemminger@vyatta.com,
tgraf@infradead.org, eric.dumazet@gmail.com,
bhutchings@solarflare.com, nhorman@tuxdriver.com,
netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH v4 1/2] net: implement mechanism for HW based QOS
Date: Tue, 04 Jan 2011 07:32:19 -0500 [thread overview]
Message-ID: <1294144339.4927.79.camel@mojatatu> (raw)
In-Reply-To: <20110104030553.13187.69135.stgit@jf-dev1-dcblab>
On Mon, 2011-01-03 at 19:05 -0800, John Fastabend wrote:
[..]
> To steer the skb we mask out the lower 4 bits of the priority
> and allow the hardware to configure upto 15 distinct classes
> of traffic. This is expected to be sufficient for most applications
> at any rate it is more then the 8021Q spec designates and is
> equal to the number of prio bands currently implemented in
> the default qdisc.
This seems very hardware specific.
i.e may be true for 8021q (or like 8021q) type hardware and therefore
your qdisc.
There are people with hardware that has thousands of hardware
flow queues (or at least give impressions as such). Maybe a naming
convention prefixed with 8021Q would be nicer or moving it into
your qdisc infrastructure and export it so drivers needing it can.
cheers,
jamal
prev parent reply other threads:[~2011-01-04 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 3:05 [net-next-2.6 PATCH v4 1/2] net: implement mechanism for HW based QOS John Fastabend
2011-01-04 3:05 ` [net-next-2.6 PATCH v4 2/2] net_sched: implement a root container qdisc sch_mclass John Fastabend
2011-01-04 6:46 ` Eric Dumazet
2011-01-04 11:18 ` Jarek Poplawski
2011-01-04 18:16 ` John Fastabend
2011-01-04 12:32 ` jamal [this message]
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=1294144339.4927.79.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jarkao2@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=shemminger@vyatta.com \
--cc=tgraf@infradead.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).