From: Eric Dumazet <dada1@cosmosbay.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: second, bigger problem with private futexes
Date: Mon, 21 May 2007 20:48:50 +0200 [thread overview]
Message-ID: <4651E992.9080205@cosmosbay.com> (raw)
In-Reply-To: <4651E44A.9070301@redhat.com>
Ulrich Drepper a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Eric Dumazet wrote:
>> Do you mean POSIX allowed to mix PROCESS_PRIVATE and PROCESS_SHARED
>> condvar and mutexes ? Seems silly to me :(
>
> Don't judge what you don't understand.
Yes, I kindly apologise for this crime.
> If all waiters are always in one
> process but the notifiers can be in different processes, this setup
> might make a lot of sense.
Thanks for providing this information.
I assume in this case the condvar is PSHARED, while mutex could be/is PRIVATE ?
I wonder how old (assuming all shared) code could work, since the notifier
would call FUTEX_CMP_REQUEUE giving a target address outside of this process vm ?
My understanding (probably bad, since I know nothing about POSIX as you mentioned)
- Old code could not use FUTEX_CMP_REQUEUE if mutex was private.
-> Old code was using a normal FUTEX_WAKE in this case.
So I repeat my question : Should we really add yer another futex command in
kernel for a corner case ?
Thanks
next prev parent reply other threads:[~2007-05-21 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 17:26 second, bigger problem with private futexes Ulrich Drepper
2007-05-21 18:15 ` Eric Dumazet
2007-05-21 18:26 ` Ulrich Drepper
2007-05-21 18:48 ` Eric Dumazet [this message]
2007-05-21 19:26 ` Eric Dumazet
2007-05-21 19:43 ` Ulrich Drepper
2007-05-21 19:55 ` Eric Dumazet
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=4651E992.9080205@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.