| 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, 1 Oct 2009 10:12:10 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Tejun Heo <tj@...nel.org> cc: jeff@...zik.org, Ingo Molnar <mingo@...e.hu>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <jens.axboe@...cle.com>, rusty@...tcorp.com.au, cl@...ux-foundation.org, dhowells@...hat.com, arjan@...ux.intel.com Subject: Re: [PATCH 19/19] workqueue: implement concurrency managed workqueue On Thu, 1 Oct 2009, Tejun Heo wrote: > > To solve the above issues, this patch implements concurrency-managed > workqueue. Ok, all the other patches in the series looked great, this one looks scary. Everything else was pretty small and targeted, and if bugs appear, bisection would show the step that was nasty. And then comes the big flag-day patch that actually introduces all the new logic, and is the most complex of the lot. Maybe it's inevitable, but if this one could be split up a bit more, I'd find the series less scary. I don't know how, though (except by adding code that simply isn't used in previous patches, and that doesn't really help anything at all), so maybe the big "switch everything over at once" thing is unavoidable. Linus -- 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