linux-kernel - Re: [4/7] dst: thread pool.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090118161041.40608174@infradead.org>
Date:	Sun, 18 Jan 2009 16:10:41 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Evgeniy Polyakov <zbr@...emap.net>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org, dst@...emap.net,
	David Howells <dhowells@...hat.com>
Subject: Re: [4/7] dst: thread pool.

On Wed, 14 Jan 2009 21:58:10 -0800
Andrew Morton <akpm@...ux-foundation.org> wrote:

> > Thread pool is used for crypto processing of incoming and outgoing
> > IO requests to reduce the overall overhead.
> 
> This is at least our fourth thread pool implementation, not counting
> kernel/workqueue.c:
>  
> 1: pdflush

I will look at moving pdflush to async function calls.. sounds like a
good "get over jetlag" project

> 
> 2: David Howells' "slow work" infrastructure

this one is *weird*. The infrastructure deals with object refcounting
somehow. 

> 
> 4: Your "dst thread pool"

from the context... I wouldn't be surprised if this can just use async
function calls as well... it's simple enough on first sight.

--
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/