David Miller wrote:
If you're asking about the virtualization scenerio, the
control node (dom0 or whatever) is the only entity which
can get at programming the filters and will set it up
properly based upon which parts of the physical device
are being exported to which guest nodes.
You're avoiding the question. Clearly guest VMs must contact the host
VM (dom0) to get real work done.
They are ultimately going to have to pass the same configuration info as
the non-virt case.
For the non-virtualized case, it's a good question.
...
But really the current hardware is just about simple queue steering,
and simple static DRR/WRED fairness algorithms applied to the queues
in hardware.
We don't need to add support for configuring anything fancy from the
start just to get something working.
Correct. But if we don't plan for the future that's currently in the
silicon pipeline, our ass will be in a sling WHEN we must figure out the
best configuration points for sub-queues.
Or are we prepared to rip out sub-queues for a non-experimental
solution, when confronted with the obvious necessity of configuring them?
You know I want multi-queue and increased parallelism it provides. A lot.
But let's not dig ourselves into a hole we must climb out of in 6-12
months. We need to think about configuration issues -now-.
Jeff
-
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
