[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.0907161513050.3814@anderson.cs.unc.edu>
Date: Thu, 16 Jul 2009 15:18:26 -0400 (EDT)
From: "James H. Anderson" <anderson@...unc.edu>
To: Raj Rajkumar <raj@....cmu.edu>
cc: Ted Baker <baker@...fsu.edu>, Noah Watkins <jayhawk@....ucsc.edu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Raistlin <raistlin@...ux.it>,
Douglas Niehaus <niehaus@...c.ku.edu>,
Henrik Austad <henrik@...tad.us>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Bill Huey <billh@...ppy.monkey.org>,
"Linux RT <linux-rt-users@...r.kernel.org> Fabio Checconi"
<fabio@...dalf.sssup.it>, Thomas Gleixner <tglx@...utronix.de>,
Dhaval Giani <dhaval.giani@...il.com>,
Tommaso Cucinotta <cucinotta@...up.it>,
Giuseppe Lipari <lipari@...is.sssup.it>,
Bjoern Brandenburg <bbb@...unc.edu>
Subject: Re: [Fwd: Re: RFC for a new Scheduling policy/class in the
Linux-kernel]
Hi Raj,
On Thu, 16 Jul 2009, Raj Rajkumar wrote:
> non-preemptive critical section. In addition, we could allow mutexes
> to either pick basic priority inheritance (desirable for local mutexes?)
> or the priority ceiling version (desirable for global mutexes shared
> across processors/cores).
This discussion when I entered it was about using global scheduling
in Linux (not partitioning), so that's what I thought the focus of the
discussion was. What's the definition of a local mutex in that case?
And how do you use ceilings under global scheduling?
Thanks.
-Jim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists