From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Alasdair G Kergon <agk@redhat.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC v2][PATCH] create workqueue threads only when needed
Date: Wed, 28 Jan 2009 09:15:39 +0100 [thread overview]
Message-ID: <1233130539.10992.38.camel@laptop> (raw)
In-Reply-To: <20090128030224.GA4867@redhat.com>
On Wed, 2009-01-28 at 04:02 +0100, Oleg Nesterov wrote:
>
> I must admit, I don't like this patch. Perhaps I am wrong, mostly I
> dislike the complications it adds.
>
> Anybody else please vote for this change?
Because you asked ;-)
I too am not particularly fond of it, for much the same reasons you
mentioned.
While I think its good to reduce the number of random kernel threads,
I'm afraid this isn't a good way to do so.
Why does everybody and his pony create their own workqueue, is that
really because it deadlocks with keventd, or are there other reasons, if
so, which, and can we solve those?
next prev parent reply other threads:[~2009-01-28 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 0:27 [RFC v2][PATCH] create workqueue threads only when needed Frederic Weisbecker
2009-01-28 3:02 ` Oleg Nesterov
2009-01-28 8:15 ` Peter Zijlstra [this message]
2009-01-28 11:33 ` Frédéric Weisbecker
2009-01-28 11:24 ` Frédéric Weisbecker
2009-01-28 23:31 ` Frederic Weisbecker
2009-01-29 4:58 ` Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233130539.10992.38.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox