| 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
| ||
|
Date: Thu, 01 Oct 2009 14:15:26 +0100 From: David Howells <dhowells@...hat.com> To: Tejun Heo <tj@...nel.org> Cc: dhowells@...hat.com, jeff@...zik.org, mingo@...e.hu, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, jens.axboe@...cle.com, rusty@...tcorp.com.au, cl@...ux-foundation.org, arjan@...ux.intel.com Subject: Re: [PATCH 19/19] workqueue: implement concurrency managed workqueue Tejun Heo <tj@...nel.org> wrote: > gcwq always keeps at least single idle worker around. When a new > worker is necessary and the worker is the last idle one, the worker > assumes the role of "manager" and manages the worker pool - > ie. creates another worker. Forward-progress is guaranteed by having > dedicated rescue workers for workqueues which may be necessary while > creating a new worker. When the manager is having problem creating a > new worker, mayday timer activates and rescue workers are summoned to > the cpu and execute works which may be necessary to create new > workers. I take it that means that the rescue-workers are donated to the pool to become worker threads (perhaps on a temporary basis) in the event that forking fails due to ENOMEM, such that resources can be freed up for fork() to use. David -- 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