Subject: Re: [PATCH] RT: Add priority-queuing and priority-inheritance to
	workqueue infrastructure
From: Daniel Walker <dwalker@mvista.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <1185969554.9513.106.camel@ghaskins-t60p.haskins.net>
References: <20070801002407.4973.54778.stgit@novell1.haskins.net>
	 <1185940340.2636.97.camel@imap.mvista.com>
	 <1185969554.9513.106.camel@ghaskins-t60p.haskins.net>
Content-Type: text/plain
Date: Wed, 01 Aug 2007 08:10:25 -0700
Message-Id: <1185981025.2636.102.camel@imap.mvista.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1175
Lines: 30

On Wed, 2007-08-01 at 07:59 -0400, Gregory Haskins wrote:
> On Tue, 2007-07-31 at 20:52 -0700, Daniel Walker wrote:
> 
> > 
> > Here's a simpler version .. uses the plist data structure instead of the
> > 100 queues, which makes for a cleaner patch ..
> 
> Hi Daniel,
> 
> I like your idea on the plist simplification a lot.  I will definitely
> roll that into my series.
> 
> I am not too psyched about using the rt_mutex_setprio() API directly,
> however.  It seems broken to be calling that directly from non rt_mutex
> code, IMHO.  Perhaps the PI subsystem should be broken out from the
> rt_mutex code so it can be used generally?  There are other areas where
> PI could potentially be used besides rt_mutex (this patch as a prime
> example), so this might make sense.

rt_mutex_setprio() is just a function. It was also designed specifically
for PI , so it seems fairly sane to use it in other PI type
situations ..

Daniel

-
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/