| 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: <20080701125357.GT14894@parisc-linux.org> Date: Tue, 1 Jul 2008 06:53:57 -0600 From: Matthew Wilcox <matthew@....cx> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: ksummit-2008-discuss@...ts.linux-foundation.org, Linux Kernel list <linux-kernel@...r.kernel.org> Subject: Re: [Ksummit-2008-discuss] Delayed interrupt work, thread pools On Tue, Jul 01, 2008 at 10:45:35PM +1000, Benjamin Herrenschmidt wrote: > In various areas (I'll come up with some examples later), kernel code > such as drivers want to defer some processing to "task level", for > various reasons such as locking (taking mutexes), memory allocation, > interrupt latency, or simply doing things that may take more time than > is reasonable to do at interrupt time or do things that may block. > > Currently, the main mechanism we provide to do that is workqueues. They > somewhat solve the problem, but at the same time, somewhat can make it > worse. Why not just use a dedicated thread? The API to start / stop threads is now pretty easy to use. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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