[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 1 Feb 2009 21:19:09 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC][PATCH] create workqueue threads only when needed
On Mon, 02 Feb 2009 08:37:41 +1100
Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
>
> > I don't know, most of those I've looked on are not documented about
> > the reason for a private workqueue. I guess most of them can use
> > the usual kevent.
>
> The main problem with kevent is that it gets clogged up.
>
> That's were thread pools kick in ... tried using Dave Howells slow
> work ?
async function calls are pretty much the same and actually in mainlinme.
Dave Howells stuff in addition plays some extremely weird refcounting
games that I cannot imagine anyone but him needing...
--
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