Subject: Re: workqueue thing
From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: torvalds@linux-foundation.org, awalls@radix.net,
       linux-kernel@vger.kernel.org, jeff@garzik.org, mingo@elte.hu,
       akpm@linux-foundation.org, jens.axboe@oracle.com, rusty@rustcorp.com.au,
       cl@linux-foundation.org, dhowells@redhat.com, arjan@linux.intel.com,
       avi@redhat.com, johannes@sipsolutions.net, andi@firstfloor.org
In-Reply-To: <4B3009DC.7020407@kernel.org>
References: <1261141088-2014-1-git-send-email-tj@kernel.org>
	 <1261143924.20899.169.camel@laptop>  <4B2EE5A5.2030208@kernel.org>
	 <1261387377.4314.37.camel@laptop>  <4B2F7879.2080901@kernel.org>
	 <1261405604.4314.154.camel@laptop>  <4B3009DC.7020407@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 22 Dec 2009 12:00:13 +0100
Message-ID: <1261479613.4937.14.camel@laptop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 937
Lines: 22

On Tue, 2009-12-22 at 08:50 +0900, Tejun Heo wrote:
> 
> >  4) didn't consider the RT needs
> 
> Can you be more specific?  What RT needs?  It's pretty difficult to
> tell when there's no in-kernel user and any shared worker pool would
> have pretty similar properties as cmwq. 

http://programming.kicks-ass.net/kernel-patches/rt-workqueue-prio/

Most of that passed over lkml too at various times and in various forms,
not eve sure that that is the last one, but its the one I found first.

Basically it boils down to letting the worklets run at the priority of
the enqueing task and boost current running works with the prio of the
highest pending work, including proper barrier support.

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