A little more information:
On a dual system:
Running as root -> Single process app (50% total CPU)-> locks out network
Running as root -> Multi process app (100% total CPU) -> locks out network
Running unprivileged -> Single process(50%) -> Network works fine
Running unprivileged -> Multi process(100%) -> locks out network
Going to try a few other network cards if I find one.
On Fri, 17 May 2002, Alan Cox wrote:
> > So the problem would appear to be that your networking *requires*
> > ksoftirqd services to function. Either:
> >
> > 1) The driver is bust - its hard_start_xmit() function is failing
> > frequently, and relying on ksoftirqd to get things done (I think;
> > it's been a while). Or
>
> The ne2k card has little buffering.
>
> > 2) Something is wrong with the ksoftirqd design. Or
>
> I think its mostly #2. We invoke ksoftirq far far too easily.
>
-- Paul N. Faure 613.266.3286 EngSoc Administrator paul-at-engsoc-dot-org Chief Technical Officer, CertainKey Inc. paul-at-certainkey-dot-com Carleton University Systems Eng. 4th Year paul-at-faure-dot-ca- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org 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 May 23 2002 - 22:00:14 EST