Re: [PATCHSET] workqueue: concurrency managed workqueue, take#4

[Tejun Heo]

Hello,

On 03/12/2010 08:23 PM, David Howells wrote:
>> 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.

Well, you can RR queue them but in general I don't think things like
that would be much of a problem for IO bounded works.  If it becomes
bad, scheduler will end up moving the source around and for most
common cases, those group queued works are gonna hit similar code
paths over and over again during their short CPU burn durations so
it's likely to be more efficient.  Are you seeing maleffects of cpu
affine work scheduling during fscache load tests?

Thank you for testing.

-- 
tejun
--
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/