Re: Traffic shaping - class ID 16bit limit?

On Thu, 25 Aug 2011 18:28:01 +0200
Miroslav Kratochvil [off-list ref] 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.

You might be able to do the same thing by splitting traffic
into multiple virtual devices (dummy or ifb) and then doing
another layer.