From: Ulrich Drepper <drepper@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pierre.Peiffer@bull.net, mingo@elte.hu,
linux-kernel@vger.kernel.org, jean-pierre.dion@bull.net
Subject: Re: [PATCH 2.6.21-rc3-mm2 4/4] sys_futex64 : allows 64bit futexes
Date: Thu, 15 Mar 2007 12:37:07 -0700 [thread overview]
Message-ID: <45F9A063.9040205@redhat.com> (raw)
In-Reply-To: <20070315113136.b04ce342.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Andrew Morton wrote:
> Well OK. But that doesn't actually explain why 64-bit mutexes are needed.
> It just says they are required.
I can show you the code but it's not easy to understand. For
complicated syn objects like rwlocks the state information is more than
just locked or not. Currently we have to use internal locks, modify the
state information, and then release it. This is terribly inefficient
when many threads are used. With 64bit futexes the state information
can be kept in the futex object and we don't need an internal lock,
hence the speed-up.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
prev parent reply other threads:[~2007-03-15 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 9:52 [PATCH 2.6.21-rc3-mm2 0/4] Futexes functionalities and improvements Pierre.Peiffer
2007-03-13 9:52 ` [PATCH 2.6.21-rc3-mm2 1/4] futex priority based wakeup Pierre.Peiffer
2007-03-13 9:52 ` [PATCH 2.6.21-rc3-mm2 2/4] Make futex_wait() use an hrtimer for timeout Pierre.Peiffer
2007-03-13 9:52 ` [PATCH 2.6.21-rc3-mm2 3/4] futex_requeue_pi optimization Pierre.Peiffer
2007-03-16 10:14 ` Peter Zijlstra
2007-03-20 15:32 ` Pierre Peiffer
2007-03-20 15:55 ` Peter Zijlstra
2007-03-20 16:32 ` Pierre Peiffer
2007-03-13 9:52 ` [PATCH 2.6.21-rc3-mm2 4/4] sys_futex64 : allows 64bit futexes Pierre.Peiffer
2007-03-15 19:07 ` Andrew Morton
2007-03-15 19:12 ` Ulrich Drepper
2007-03-15 19:31 ` Andrew Morton
2007-03-15 19:37 ` Ulrich Drepper [this message]
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=45F9A063.9040205@redhat.com \
--to=drepper@redhat.com \
--cc=Pierre.Peiffer@bull.net \
--cc=akpm@linux-foundation.org \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).