From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Jens Axboe <axboe@kernel.dk>, Jeff Garzik <jeff@garzik.org>,
David Howells <dhowells@redhat.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Suresh Jayaraman <sjayaraman@suse.de>,
Steven Whitehouse <swhiteho@redhat.com>,
Steve French <sfrench@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andy Walls <awalls@radix.net>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [GIT PULL] workqueue for v2.6.36
Date: Wed, 04 Aug 2010 19:53:15 +0200 [thread overview]
Message-ID: <4C59A90B.8040403@s5r6.in-berlin.de> (raw)
In-Reply-To: <1280939168.21608.10.camel@c-dwalke-linux.qualcomm.com>
Daniel Walker wrote:
> I haven't seen anything that shows your adding back the same
> expressiveness that your removing .. So I still don't think this should
> be merged.
Do you mean by expressiveness the ability to hack around a suboptimally
working driver in userland (by requiring the administrator to play with
kernel thread priorities of dedicated worker threads)? Is it known
whether this driver/ these drivers still require this hack after Tejun's
patch set is applied? If yes, how about finding someone to fix this
driver for good. Meanwhile, let's gets rid of the problem of having
both too few and too many workers in countless present usages of the
workqueue API please.
--
Stefan Richter
-=====-==-=- =--- --=--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-08-04 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 13:37 Tejun Heo
2010-08-04 16:26 ` Daniel Walker
2010-08-04 17:53 ` Stefan Richter [this message]
2010-08-04 18:03 ` Daniel Walker
2010-08-09 20:05 ` Linus Torvalds
2010-08-09 20:09 ` Markus Trippelsdorf
2010-08-09 20:18 ` Linus Torvalds
2010-08-09 21:29 ` Tejun Heo
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=4C59A90B.8040403@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=awalls@radix.net \
--cc=axboe@kernel.dk \
--cc=cl@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dwalker@codeaurora.org \
--cc=fweisbec@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=oleg@redhat.com \
--cc=sfrench@samba.org \
--cc=sjayaraman@suse.de \
--cc=swhiteho@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®