From: Stephen Hemminger <shemminger@vyatta.com>
To: Miroslav Kratochvil <exa.exa@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Traffic shaping - class ID 16bit limit?
Date: Thu, 25 Aug 2011 10:10:38 -0700 [thread overview]
Message-ID: <20110825101038.6b8c3e02@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <CAO0uZ+_6xC0gymfbu28PRK4SaVgkGaSbbe-PgXvZ4h-cPp8k2A@mail.gmail.com>
On Thu, 25 Aug 2011 19:06:58 +0200
Miroslav Kratochvil <exa.exa@gmail.com> wrote:
> >> Technically the ClassID seems to be "hardcoded" as a 16bit value, but
> >> after some source searching, I haven't found any good reason for it to
> >> be 16-bit only.
> >
> > Granted it was a poor choice in the initial design.
> > It is wired into the API and changing it would be quite painful.
> >
>
> I was feeling something like that would come.
>
> If I get it correctly, the API change would consist of:
>
> - some netlink protocol change
> - slight modification of qdisc_class_hash
> - modifications in all (four?) hierarchical schedulers
> - tiny expansion of userspace tc utility
And all the magic compatiablity layers to make old code
work with new code.
next prev parent reply other threads:[~2011-08-25 17:10 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 [this message]
2011-08-26 16:53 ` David Miller
2011-08-25 20:26 ` jamal
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=20110825101038.6b8c3e02@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=exa.exa@gmail.com \
--cc=netdev@vger.kernel.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).