[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1233554443.18767.71.camel@pasglop>
Date: Mon, 02 Feb 2009 17:00:43 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Arjan van de Ven <arjan@...radead.org>,
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, 2009-02-02 at 03:24 +0100, Frederic Weisbecker wrote:
> On Mon, Feb 02, 2009 at 08:37:41AM +1100, Benjamin Herrenschmidt 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.
>
>
> I don't think so. Here is a snapshot of the workqueue tracer in my
> box currently:
That's not quite what I meant ...
The main problem with keventd I'd say is that it's used in all sort of
exeptional code path (ie, driver reset path, error handling, etc...) for
things that will msleep happily for tenth milliseconds, that sort of
thing.
IE. It will be pretty responsive -in general- but can suffer form
horrible latencies every now and then.
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