Thread (40 messages) 40 messages, 9 authors, 2007-05-11

Re: [PATCH] IPROUTE: Modify tc for new PRIO multiqueue behavior

From: David Miller <davem@davemloft.net>
Date: 2007-05-04 20:06:33

From: Stephen Hemminger <redacted>
Date: Fri, 4 May 2007 13:01:10 -0700
Just because they want to standardize, and put it in hardware doesn't
mean it is a good idea and Linux needs to support it!

Why is it better for hardware to make the "next packet to send" decision?
For wired ethernet, I can't see how adding the complexity of fixed number
of small queues is a gain. Better to just do the priority decision in software
and then queue it to the hardware. This seems like the old Token Ring
and MAP/TOP style crap crammed on top of Ethernet.
I suspect perhaps the real impetus behind this facility is not being
disclosed.

It certainly is not going to be faster to do this in hardware.

I myself don't see why in the world one would want to do this in
hardware either.  Software can do the selection fast enough and with
tons more flexibility.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help