Re: Overview of concurrency managed workqueue

From: Daniel Walker
Date: Thu Jun 17 2010 - 18:29:10 EST


On Wed, 2010-06-16 at 15:45 +0200, Tejun Heo wrote:
> On 06/16/2010 03:41 PM, Daniel Walker wrote:
> > Any workqueue that has a thread which can be prioritized from userspace.
> > As long as there is a thread it can usually be given a priority from
> > userspace, so any _current_ workqueue which uses a single thread or
> > multiple threads is an example of what I'm talking about.
>
> Eh... what's the use case for that? That's just so wrong. What do
> you do after a suspend/resume cycle? Reprioritize all of them from
> suspend/resume hooks?


I tested your assertion about suspend/resume, and it doesn't seem to be
true.. I tested workqueues with nice levels, and real time priorities on
a random laptop using 2.6.31 both held their priorities across suspend
to RAM and suspend to disk .. Was this change added after 2.6.31 ?

Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/