Re: NPTL mutex and the scheduling priority

On Mon, 2006-06-12 at 17:10 +0900, Atsushi Nemoto wrote:
> # This is a copy of message posted libc-alpha ML.  I want to hear from
> # kernel people too ...
> 
> Hi.  I found that it seems NPTL's mutex does not follow the scheduling
> parameter.  If some threads were blocked by getting a single
> mutex_lock, I expect that a thread with highest priority got the lock
> first, but current NPTL's behaviour is different.
\

you want to use the PI futexes that are in 2.6.17-rc5-mm tree

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

---

• Follow-Ups:
  • Re: NPTL mutex and the scheduling priority
    • From: Jakub Jelinek <[email protected]>

• References:
  • NPTL mutex and the scheduling priority
    • From: Atsushi Nemoto <[email protected]>

• Prev by Date: Re: [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content)
• Next by Date: [PATCH 1/7] fuse: use MISC_MAJOR
• Previous by thread: NPTL mutex and the scheduling priority
• Next by thread: Re: NPTL mutex and the scheduling priority
• Index(es):
  • Date
  • Thread

[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]