| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4B99CB0F.1090505@kernel.org> Date: Fri, 12 Mar 2010 14:03:11 +0900 From: Tejun Heo <tj@...nel.org> To: David Howells <dhowells@...hat.com> CC: torvalds@...ux-foundation.org, mingo@...e.hu, peterz@...radead.org, awalls@...ix.net, linux-kernel@...r.kernel.org, jeff@...zik.org, akpm@...ux-foundation.org, jens.axboe@...cle.com, rusty@...tcorp.com.au, cl@...ux-foundation.org, arjan@...ux.intel.com, avi@...hat.com, johannes@...solutions.net, andi@...stfloor.org, oleg@...hat.com Subject: Re: [PATCHSET] workqueue: concurrency managed workqueue, take#4 Hello, On 03/10/2010 11:52 PM, David Howells wrote: > * queue_work - queue work on a workqueue > * @wq: workqueue to use > * @work: work to queue > * > * Returns 0 if @work was already on a queue, non-zero otherwise. > * > * We queue the work to the CPU on which it was submitted, but if the CPU dies > * it can be processed by another CPU. > > 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. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists