Re: [PATCH 34/35] async: use workqueue for worker pool

From: Arjan van de Ven
Date: Tue Jun 29 2010 - 12:41:06 EST

On 6/29/2010 8:55 AM, Tejun Heo wrote:

On 06/29/2010 05:52 PM, Frederic Weisbecker wrote:
If there is a question of slow ports to probe, then cmwq wouldn't seem the
right thing here, as it only forks when we go to sleep.
I lost you here. If something during boot has to burn cpu cycles
(which it shouldn't, really), it has to burn cpu cycles and having
multiple concurent threads won't help anything.
It would on SMP.
Oh, I see. Parallel cpu hogs. We don't have such users for async and
I think using padata would be the right solution for those situations.

uh? clearly the assumption is that if I have a 16 CPU machine, and 12 items of work get scheduled,
that we get all 12 running in parallel. All the smarts of cmwq surely only kick in once you've reached the
"one work item per cpu" threshold ???

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at