Re: [PATCHSET] workqueue: concurrency managed workqueue, take#4
From: David Howells
Date: Fri Mar 12 2010 - 06:26:19 EST
Tejun Heo <tj@xxxxxxxxxx> wrote:
> > So when a work item is running on a CPU, any work items it queues
> > (including requeueing itself) will be queued upon that CPU for attention
> > only by that CPU (assuming that CPU doesn't get pulled out)?
>
> Yes, that's the one of the characteristics of workqueue. For IO bound
> stuff, it usually is a plus.
Hmmm. So when, say, an FS-Cache index object finishes creating itself on disk
and then releases all the several thousand data objects waiting on that event
so that they can then create themselves, it will do this by calling
queue_work() on each of them in turn. I take it this will stack them all up on
that one CPU's work queue.
David
--
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/