[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100617161619.d3ebd73d.akpm@linux-foundation.org>
Date: Thu, 17 Jun 2010 16:16:19 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andy Walls <awalls@...metrocast.net>
Cc: Daniel Walker <dwalker@...eaurora.org>, Tejun Heo <tj@...nel.org>,
mingo@...e.hu, linux-kernel@...r.kernel.org, jeff@...zik.org,
rusty@...tcorp.com.au, cl@...ux-foundation.org,
dhowells@...hat.com, arjan@...ux.intel.com,
johannes@...solutions.net, oleg@...hat.com, axboe@...nel.dk
Subject: Re: Overview of concurrency managed workqueue
On Thu, 17 Jun 2010 08:01:06 -0400
Andy Walls <awalls@...metrocast.net> wrote:
> I'm going to agree with Tejun, that tweaking worker thread priorities
> seems like an odd thing, since they are meant to handle deferable
> actions - things that can be put off until later.
Disagree. If you're in an interrupt handler and have some work which
you want done in process context and you want it done RIGHT NOW then
handing that work off to a realtime-policy worker thread is a fine way of
doing that.
--
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