Re: Overview of concurrency managed workqueue

[Daniel Walker]

On Tue, 2010-06-15 at 20:25 +0200, Tejun Heo wrote:
> Hello, all.
> 
> So, here's the overview I wrote up today.  If anything needs more
> clarification, just ask.  Thanks.
> 
> == Overview
> 
> There are many cases where an execution context is needed and there
> already are several mechanisms for them.  The most commonly used one
> is workqueue and there are slow_work, async and a few other.  Although
> workqueue has been serving the kernel for quite some time now, it has
> some limitations.

I noticed that you removed the RT workqueue since it's no longer used,
but it's possible that a user can raise the priority of a given work
queue thread into real time priorities. So with single threaded, and
multithreaded workqueues specific to certain areas of the kernel the
user would have a greater ability to control priorities of those areas.

It looks like with your patches it would remove that level of
flexability effectively making all the work item the same priority with
no ability to raise or lower .. Is that accurate ?

btw, Thanks for the write up.

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/