[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[altq 195] Re: Overcommitting Classes...
Karl Pielorz wrote:
> I have another question...
> Which is quite true / correct - we're trying to overcommit the bandwidth.
> The previous versions of AltQ/CBQ would 'warn' about overcommit but would run
> with it...
This behavior is a by-product (or side-effect) of integration of
admission control into the altq library. And I think it is the right
> Is there anyway we can get round this? - Perhaps by 'prioritising' the queues?
> - Maybe then we can have the 'default' class at a higher priority than the
> other classes, so they only get their share of the bandwidth _after_ the
> default class has been processed...
> Or is there a way of giving children classes 'up' to their maximum kbs,
> without reserving the bandwidth out of the root class?
I don't understand what you are trying to achieve by overcommitting
bandwidth. Could you elaborate on it?
From the implementation's point of view, it is easy to add a flag to
allow bandwidth overcommit. But I haven't been convinced of its