Messages in this thread | | | Subject | Re: Overview of concurrency managed workqueue | From | Daniel Walker <> | Date | Thu, 17 Jun 2010 15:28:53 -0700 |
| |
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
| |