jamal wrote:
On Mon, 2006-16-01 at 05:35 +0100, Patrick McHardy wrote:
2) If i specify 4 queues, without this, i get a priomap which says how
to map to 3 queues. I really should specify mapping to 4 queues.
This is where we disagree. Prio includes a mechanism for classification
without priomap, so its not neccessary that priomap includes all bands.
Indeed this is where we disagree.
It is also not necessary to assume that all bands are fifo ;->
I don't see how this is related.
This is a decision that needs to be made by something smarter than the
kernel (the policy decision point - i.e user space).
So you're fine with having a default picked by the kernel for all bands
contained in priomap, but not for others, even though the users told
the kernel to add the other bands? That doesn't convince me.
Nothing is made harder at all.
Well no, but the patch which started this thread intended to make the
case where priomap is not used easier by creating inner qdiscs for
all bands instead of just the ones contained in priomap. In the
case where priomap is used nothing really changes, because by default
all bands are contained in it anyway.
Ok, I will make it simpler:
Should tc configure 3 bands in the priomap if i specify 2 bands?
It does.
If it does the kernel will reject it.
Extend that arguement to if i specified 10 bands, should the
priomap only contain 3 bands?
To put it simple: I don't care about priomap. It is one of two
mechanisms to classify in the prio qdisc and it makes no sense
to force users to use it.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
