Hello!
> If you call netif_wake_queue() within the hard_start_xmit() handler and
> if you have another skb queued then your hard_start_xmit() handler will
> be called again really soon by the softirq stuff (at the exit from the
> next irq, syscall or exception handler), often before the current packet
> has been sent. Your driver may well choke on this. Also correct?
Not correct. If driver has no room to queue next packet,
it does not wake itself, certainly.
> and many others.
All the drivers do this. It is not related to softnet, drivers always
worked in this way. Only without softnet, if was statement "dev->tbusy=0".
The rest is well explained in Jaml's paper.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:20 EST