From: Jamal Hadi Salim <[EMAIL PROTECTED]> Date: Sat, 23 Jul 2005 10:14:52 -0400
> Setting the skb->prio to be used by the driver sounds reasonable. > Another alternative would be what was already mentioned to change the > call to hardware_start_transmit() to take a prio option. > The driver should take care of what that all means given that we have > views that differ depending on the h/ware. But this simply doesn't work by itself, that's why we need the per-queue "stopped" states. We need something that properly synchronizes the queue "full" state transitions, so that the queue does not deadlock and when one priority queue fills up, we do the right thing. All of the packet scheduler is keyed off of being able to atomically "send the queue X while not stopped", and that transition from stopped to not-stopped is interlocked properly with the asynchronous sending path. Alexey explained this to both you and I about 3 years ago. At the time we were talking about the prioritized queues provides by a few gigabit NICs at the time. - 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
