diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2006-06-19 23:57:59 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2006-06-19 23:57:59 -0700 |
commit | 48d83325b61043e3bbd24dd37b9fe433744cf330 (patch) | |
tree | 00dc0682be0f096676ac885152b4ae14c4137338 /include/linux | |
parent | d6cc7f1a3b33c89c91b3dfce1ff053178893470e (diff) | |
download | lwn-48d83325b61043e3bbd24dd37b9fe433744cf330.tar.gz lwn-48d83325b61043e3bbd24dd37b9fe433744cf330.zip |
[NET]: Prevent multiple qdisc runs
Having two or more qdisc_run's contend against each other is bad because
it can induce packet reordering if the packets have to be requeued. It
appears that this is an unintended consequence of relinquinshing the queue
lock while transmitting. That in turn is needed for devices that spend a
lot of time in their transmit routine.
There are no advantages to be had as devices with queues are inherently
single-threaded (the loopback device is not but then it doesn't have a
queue).
Even if you were to add a queue to a parallel virtual device (e.g., bolt
a tbf filter in front of an ipip tunnel device), you would still want to
process the queue in sequence to ensure that the packets are ordered
correctly.
The solution here is to steal a bit from net_device to prevent this.
BTW, as qdisc_restart is no longer used by anyone as a module inside the
kernel (IIRC it used to with netif_wake_queue), I have not exported the
new __qdisc_run function.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux')
-rw-r--r-- | include/linux/netdevice.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h index e432b743dda2..39919c882a25 100644 --- a/include/linux/netdevice.h +++ b/include/linux/netdevice.h @@ -233,6 +233,7 @@ enum netdev_state_t __LINK_STATE_RX_SCHED, __LINK_STATE_LINKWATCH_PENDING, __LINK_STATE_DORMANT, + __LINK_STATE_QDISC_RUNNING, }; |