[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1229544192.16253.37.camel@pasglop>
Date: Thu, 18 Dec 2008 07:03:12 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Evgeniy Polyakov <zbr@...emap.net>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>
Subject: Re: [4/7] dst: thread pool.
> 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.
The idea after KS was to use David Howells slow_work, maybe massaging
the interfaces a bit.
I haven't had time to dedicate to that yet myself. David, what are you
up to with your initial implementation ?
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/
Powered by blists - more mailing lists