| 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: Tue, 29 Jul 2014 23:46:06 -0400 From: Tejun Heo <tj@...nel.org> To: Lai Jiangshan <laijs@...fujitsu.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH RFC 2/2 V2] workqueue: use dedicated creater kthread for all pools On Wed, Jul 30, 2014 at 11:46:02AM +0800, Lai Jiangshan wrote: > It add complexity to other things but not the code. The code is simplified. How? It can simply repeat kthread_create() until it succeeds with msleep() inbetween. How can that be more complex than what's implemented now? > And failed pool is much fewer than creation which is completely coincidental, > and after cooldown time, the other pool may also create worker. I don't follow the above at all. Can you please elaborate? 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