From: jamal <hadi@cyberus.ca>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Miroslav Kratochvil <exa.exa@gmail.com>, netdev@vger.kernel.org
Subject: Re: Traffic shaping - class ID 16bit limit?
Date: Thu, 25 Aug 2011 16:26:53 -0400 [thread overview]
Message-ID: <1314304013.2329.3.camel@mojatatu> (raw)
In-Reply-To: <20110825093937.2a8a1457@nehalam.ftrdhcpuser.net>
On Thu, 2011-08-25 at 09:39 -0700, Stephen Hemminger wrote:
> Granted it was a poor choice in the initial design.
> It is wired into the API and changing it would be quite painful.
>
You should be able to have infinite queues if you use the
hierachies. i.e each hierachy should expose a new 16 bit
namespace.
cheers,
jamal
prev parent reply other threads:[~2011-08-25 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 16:28 Traffic shaping - class ID 16bit limit? Miroslav Kratochvil
2011-08-25 16:39 ` Stephen Hemminger
2011-08-25 17:06 ` Miroslav Kratochvil
2011-08-25 17:10 ` Stephen Hemminger
2011-08-26 16:53 ` David Miller
2011-08-25 20:26 ` 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=1314304013.2329.3.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=exa.exa@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).