public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Peiffer <pierre.peiffer@bull.net>
To: Daniel Walker <dwalker@mvista.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Dinakar Guniguntala" <dino@in.ibm.com>,
	"Jean-Pierre Dion" <jean-pierre.dion@bull.net>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Ulrich Drepper" <drepper@redhat.com>,
	"Jakub Jelinek" <jakub@redhat.com>,
	"Darren Hart" <dvhltc@us.ibm.com>,
	"Sébastien Dugué" <sebastien.dugue@bull.net>
Subject: Re: [PATCH 2.6.20-rc4 1/4] futex priority based wakeup
Date: Wed, 10 Jan 2007 17:29:40 +0100	[thread overview]
Message-ID: <45A51474.3040906@bull.net> (raw)
In-Reply-To: <1168445501.22579.7.camel@imap.mvista.com>

Daniel Walker a écrit :
> On Tue, 2007-01-09 at 17:16 +0100, Pierre Peiffer wrote:
>> @@ -1358,7 +1366,7 @@ static int futex_unlock_pi(u32 __user *u
>>         struct futex_hash_bucket *hb;
>>         struct futex_q *this, *next;
>>         u32 uval;
>> -       struct list_head *head;
>> +       struct plist_head *head;
>>         union futex_key key;
>>         int ret, attempt = 0;
>>
>> @@ -1409,7 +1417,7 @@ retry_locked:
>>          */
>>         head = &hb->chain;
>>
>> -       list_for_each_entry_safe(this, next, head, list) {
>> +       plist_for_each_entry_safe(this, next, head, list) {
>>                 if (!match_futex (&this->key, &key))
>>                         continue;
>>                 ret = wake_futex_pi(uaddr, uval, this);
> 
> 
> Is this really necessary? The rtmutex will priority sort the waiters
> when you enable priority inheritance. Inside the wake_futex_pi() it
> actually just pulls the new owner off another plist inside the the
> rtmutex structure.

Yes. ... necessary for non-PI-futex (ie "normal" futex)...

As the hash_bucket_list is used and common for both futex and PI-futex, yes, in 
case of PI_futex, the task is queued two times in two plist.

-- 
Pierre

  reply	other threads:[~2007-01-10 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45A3B330.9000104@bull.net>
2007-01-09 16:16 ` [PATCH 2.6.20-rc4 1/4] futex priority based wakeup Pierre Peiffer
2007-01-09 16:29   ` Ulrich Drepper
2007-01-10 11:47     ` Pierre Peiffer
2007-01-10 12:03       ` Pierre Peiffer
2007-01-10 12:54       ` Jakub Jelinek
2007-01-10 15:05         ` Pierre Peiffer
2007-01-10 18:15           ` Ulrich Drepper
2007-01-11  7:20       ` Ulrich Drepper
2007-01-09 17:59   ` Daniel Walker
2007-01-10 16:11   ` Daniel Walker
2007-01-10 16:29     ` Pierre Peiffer [this message]
2007-01-10 16:33       ` Daniel Walker
2007-01-09 16:16 ` [PATCH 2.6.20-rc4 2/4] Make futex_wait() use an hrtimer for timeout Pierre Peiffer
2007-01-09 16:20 ` [PATCH 2.6.20-rc4 3/4] futex_requeue_pi optimization Pierre Peiffer
2007-01-09 16:33   ` Ulrich Drepper
2007-01-10  8:17     ` Pierre Peiffer
2007-01-10  8:24       ` Ulrich Drepper
2007-01-09 16:25 ` [PATCH 2.6.20-rc4 4/4][RFC] sys_futex64 : allows 64bit futexes Pierre Peiffer
2007-01-11 21:49   ` Andrew Morton
2007-01-11 22:14   ` Jakub Jelinek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45A51474.3040906@bull.net \
    --to=pierre.peiffer@bull.net \
    --cc=dino@in.ibm.com \
    --cc=drepper@redhat.com \
    --cc=dvhltc@us.ibm.com \
    --cc=dwalker@mvista.com \
    --cc=jakub@redhat.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sebastien.dugue@bull.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox