| 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: <20080702024719.GV29319@disturbed> Date: Wed, 2 Jul 2008 12:47:19 +1000 From: Dave Chinner <david@...morbit.com> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: Dean Nelson <dcn@....com>, Robin Holt <holt@....com>, ksummit-2008-discuss@...ts.linux-foundation.org, Linux Kernel list <linux-kernel@...r.kernel.org> Subject: Re: Delayed interrupt work, thread pools On Wed, Jul 02, 2008 at 12:38:52PM +1000, Benjamin Herrenschmidt wrote: > On Tue, 2008-07-01 at 20:39 -0500, Dean Nelson wrote: > > As Robin, mentioned XPC manages a pool of kthreads that can (for performance > > reasons) be quickly awakened by an interrupt handler and that are able to > > block for indefinite periods of time. > > > > In drivers/misc/sgi-xp/xpc_main.c you'll find a rather simplistic attempt > > at maintaining this pool of kthreads. ..... > > I'd love it if a general mechanism were provided so that XPC could get out > > of maintaining its own pool. > > Thanks. That makes one existing in-tree user and a one likely WIP user, > probably enough to move forward :-) FWIW, the NFS server has a fairly sophisicated thread pool implementation that allows interesting control of pool affinity. Look up struct svc_pool in your local tree ;) Cheers, Dave. -- Dave Chinner david@...morbit.com -- 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