|| ||Daniel Walker <dwalker-AT-codeaurora.org> |
|| ||Tejun Heo <tj-AT-kernel.org> |
|| ||Re: Overview of concurrency managed workqueue |
|| ||Wed, 16 Jun 2010 06:41:04 -0700|
|| ||mingo-AT-elte.hu, awalls-AT-radix.net, linux-kernel-AT-vger.kernel.org,
jeff-AT-garzik.org, akpm-AT-linux-foundation.org, rusty-AT-rustcorp.com.au,
arjan-AT-linux.intel.com, johannes-AT-sipsolutions.net, oleg-AT-redhat.com,
|| ||Article, Thread
On Wed, 2010-06-16 at 15:30 +0200, Tejun Heo wrote:
> On 06/16/2010 03:27 PM, Daniel Walker wrote:
> >> Yes, that is. With new cmwq, a wq can't assume association with
> >> specific kthread and thus can't use wq as simple frontend to kthreads,
> >> but if somebody wants dedicated kthreads instead of shared ones in
> >> units of work, [s]he should be using kthread.
> > I'm not talking about coders using workqueues when they should be using
> > kthreads .. We're talking about currently existing workqueues. Aren't
> > you converting all _current_ workqueues to your system?
> Yes, sure I'm but which current users are you talking about?
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.
to post comments)