[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081217233934.GB30039@ioremap.net>
Date: Thu, 18 Dec 2008 02:39:35 +0300
From: Evgeniy Polyakov <zbr@...emap.net>
To: Arnd Bergmann <arnd@...db.de>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [4/7] dst: thread pool.
Hi Arnd.
On Wed, Dec 17, 2008 at 04:55:04PM +0100, Arnd Bergmann (arnd@...db.de) wrote:
> Have you looked at the last discussion involving thread pools in Linux?
> BenH brought up the topic earlier this year, it is archived on
> https://lists.linux-foundation.org/pipermail/ksummit-2008-discuss/2008-July/000213.html
>
> So while it seems that there is clearly a use for such infrastructure,
> my feeling is that it should not be part of dst, but rather live
> in a location where it can be used by every subsystem.
>
> Of course getting it there means another flame war^W^W discussion about what
> the right interface should look like.
>
> My personal feeling is that the interface should look a lot like
> the existing work queues, to the point where you can easily convert
> drivers between them, or even move all work queues over to thread pools.
As Benjamin said, it was decided to use David Howells work. I hope it
will allow simple usage model DST has, but since there is no code yet, I
have my own.
If David will not push it upstream I think it could be possible to move
DST's thread pool outside of the storage project. I can review any
submitted pool implementation if being copied, but so far will carry own
implementation in the DST sources. If David will not push his code we
can return to my implementation.
--
Evgeniy Polyakov
--
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