Ben Greear writes:
> I happened to notice that my ksoftirqd_CPU0 process started spinning
> at 99% CPU when I plugged in the ports to a tulip NIC. I didn't see
> any significant amount of interrupts when I looked at /proc/interrupts,
> and there was no traffic running.
> However, this is also running a hacked up tulip-napi driver, so it
> could very well be my problem. I have not seen this on any other kernel
> in several months though...
> Anyway, if anyone has seen this, I'd like to know. Otherwise, I'll blame
> my code and start poking at things...
Well it can be normal operation if box is highly loaded...
At high loads network interrupts are disabled not to trash performance or
DoS the kernel. Which in turn does succesive polls via RX-softirq to devices
at rate the it can process. So no interrupts when resources are scarce.
The lack of interrupts makes ksoftirqd run the RX-softirq so the network load
becomes visable here. Also review the discussion about ksoftirqd priority.
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 : Thu Jan 23 2003 - 22:00:31 EST