Re: [PATCH 19/19] workqueue: implement concurrency managed workqueue
[Posted October 7, 2009 by corbet]
| From: |
| Andrew Morton <akpm-AT-linux-foundation.org> |
| To: |
| Tejun Heo <tj-AT-kernel.org> |
| Subject: |
| Re: [PATCH 19/19] workqueue: implement concurrency managed workqueue |
| Date: |
| Thu, 1 Oct 2009 07:49:59 -0700 |
| Cc: |
| jeff-AT-garzik.org, mingo-AT-elte.hu, linux-kernel-AT-vger.kernel.org,
jens.axboe-AT-oracle.com, rusty-AT-rustcorp.com.au,
cl-AT-linux-foundation.org, dhowells-AT-redhat.com, arjan-AT-linux.intel.com |
| Archive-link: |
| Article, Thread
|
On Thu, 1 Oct 2009 17:09:18 +0900 Tejun Heo <tj@kernel.org> wrote:
> To solve the above issues, this patch implements concurrency-managed
> workqueue.
Seems reasonable.
This approach would appear to rule out the option of setting a work
thread's state (scheduling policy, scheduling priority, uid, etc) to
anything other than some default.
I guess that's unlikely to be a problem if we haven't yet had a need to
do that, but I'd be a bit surprised to discover that nobody has done
that sort of thing yet? Nobody has niced up their workqueue threads?
(
Log in to post comments)