Re: [Ksummit-2008-discuss] Delayed interrupt work, thread pools

[Eric W. Biederman]

Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> writes:

> The question is: is that significantly less overhead than just spawning
> a new full blown kernel thread ? enough to justify the complexity ? at
> the end of the day, it means allocating a stack (which on ppc64 is still
> 16K, I know it sucks)... 

I looked at this a while ago.  And right  now kernel_thread is fairly light.
kthread_create has latency issues because we need to queue up a task on
our kernel thread spawning daemon, and let it fork the child.  Needing
to go via the kthread spawning daemon didn't look fundamental, just something
that was a challenge to sort out.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/