[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1280944987.21608.53.camel@c-dwalke-linux.qualcomm.com>
Date: Wed, 04 Aug 2010 11:03:07 -0700
From: Daniel Walker <dwalker@...eaurora.org>
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Tejun Heo <tj@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
lkml <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Jens Axboe <axboe@...nel.dk>, Jeff Garzik <jeff@...zik.org>,
David Howells <dhowells@...hat.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Suresh Jayaraman <sjayaraman@...e.de>,
Steven Whitehouse <swhiteho@...hat.com>,
Steve French <sfrench@...ba.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Andy Walls <awalls@...ix.net>,
Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [GIT PULL] workqueue for v2.6.36
On Wed, 2010-08-04 at 19:53 +0200, Stefan Richter wrote:
> 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.
I mean by expressiveness the fact that a user can prioritize their
system more fully in the current system.
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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