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: <1229561507.19360.0.camel@pasglop>
Date:	Thu, 18 Dec 2008 11:51:47 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Evgeniy Polyakov <zbr@...emap.net>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>
Subject: Re: [4/7] dst: thread pool.


> I have no objections against any implementation which will be imported
> into the tree and can change the code to use new API quickly, but since
> there is no code right now, I created my own thread pool.

Heh. I think I counted 3 or 4 thread pool implementations already in the
kernel though they are all ad-hoc attached to a given subsystem.

> Particulary DST needs ability to sleep or queue the work to be processed
> by the pool and API to flush/destroy the pool.

Cheers,
Ben.

--
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/