lkml.org 
[lkml]   [2010]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCHSET] workqueue: concurrency managed workqueue, take#4
Date
Tejun Heo <tj@kernel.org> 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


\
 
 \ /
  Last update: 2010-03-12 12:29    [W:0.479 / U:0.364 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site