On Tue, 2006-04-18 at 09:14 -0700, Daniel Walker wrote:
>
> > Actually, I always thought that running PREEMPT_DESKTOP with soft and hard
> > IRQS as threads was priority ceiling. It's just that all locks have the
> > priority of MAX_RT_PRIO (no preemption allowed). OK, this doesn't apply
> > to mutexes, but it does apply for spin_locks. :)
>
> Interesting way to look at it .
>
> Reminds me of the RT read/write locks, only one read or one writer at a
> time, so it's really just a mutex ..
>
We'll read/write doesn't work well with PI (or latencies for that
matter). But rw_locks have one advantage over normal rt_mutex, and that
is they are self recursive. i.e. one rw_lock can be taken over and over
again (as read) by the same process, as long as it releases it the same
amount of times.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
