> Acckk!!! I just saw that someone put netif_wake_queue() in the normal path
> of the 3c59x.c Tx routine! This is BAD. That is putting an expensive call
> in the critical path, and it's not even the right semantics.
Well, do not stop queue, then there will be no reasons to wake it.
If we stop queue, we have to wake it.
> Most machines could never see a regime where they are overwhelmed by just
> accepting incoming packets. In the situation where it occurs, usually only
> gigabit cards or multiple 100baseTx connections, there must be
> discard/ignore policy.
Khm... Please, get some simple benchmark applet sort of netperf
and enjoy with this impossible phenomenon on single 100Mbit interface.
Despite of all the "max job on interrupt" linux-2.2 never leaves irq handler
and does no job in result. BSD (and NT, by a strange reason)
with their silly approach _work_ at any load level, by the way.