On Mon, 23 Jul 2001, Andrea Arcangeli wrote:
> here the one in netif_rx:
> __cpu_raise_softirq(this_cpu, NET_RX_SOFTIRQ);
> The first netif_rx is required to run from interrupt handler (otherwise
> we should have executed cpu_raise_softirq and not __cpu_raise_softirq)
> so we cannot miss the do_softirq in the return path from do_IRQ() and so
> we cannot wait for the next incoming interrupt (if we have a overflow of
> the do_softirq loop ksoftirqd will take care of it without waiting for
> the next interrupt as it could instead happen in old 2.4 kernels).
Hmmh, wait a second. I take it that means calling netif_rx not from
hard-irq context, but e.g. from bh is a bug? (Even if the only consequence
is delaying the processing by up to one timer tick?)
If so, I believe this bug exists in a couple of a places. One example is -
of course - the ISDN code, where netif_rx() is called from bh context. But
I would think that e.g. ppp_generic is affected as well.
Could you clarify this? Maybe adding something like the following to
netif_rx() is a good idea?
printk(KERN_WARNING "netif_rx called not in_irq() from %p\n",
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 23 2001 - 21:00:16 EST