From: "Qinghua(Kevin) Ye" <[EMAIL PROTECTED]> Date: Wed, 6 Jul 2005 14:12:29 -0600
> Yes, you are right. Click acturally will release the CPU to OS at interval. > Other processes will be responded at this interval. It is not Click's right to make this kind of decision, that is what we have the process scheduler for. > The goal of polling extension is to reduce the interrupt overhead and > improve the throughput, especailly the small packets. NAPI does solve this > problem to some extend. And the extent to which NAPI does not solve this problem is??? Please propose something that solves this problem better and still respects the other processes and resources in the system. > If not use polling, how can I make use of all the CPUs to process packets? > Can I make all of the CPUs run SOFTIRQ and IRQ code simultaneously? It seems > there is only one ksoftirqd process busy dealing with process, while the > other ksoftirqd is idle in my system. There is one ksoftirqd for each cpu in the system. All the network card interrupts are arriving at that one cpu on your machine, so the other ksoftirqd doesn't have any work to do. If ksoftirqd is running very often, this means that network processing is consuming an enormous amount of your cpu. So it gets scheduled to a process and thus the packet processing is properly shared with other processes on the system and nobody is starved out. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
