From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre.Peiffer@bull.net
Cc: mingo@elte.hu, drepper@redhat.com, linux-kernel@vger.kernel.org,
jean-pierre.dion@bull.net, pierre.peiffer@bull.net
Subject: Re: [PATCH 2.6.21-rc3-mm2 4/4] sys_futex64 : allows 64bit futexes
Date: Thu, 15 Mar 2007 11:07:52 -0800 [thread overview]
Message-ID: <20070315110752.f1df4509.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070313095549.813330645@bull.net>
> On Tue, 13 Mar 2007 10:52:07 +0100 Pierre.Peiffer@bull.net wrote:
> This last patch is an adaptation of the sys_futex64 syscall provided in -rt
> patch (originally written by Ingo). It allows the use of 64bit futex.
>
> I have re-worked most of the code to avoid the duplication of the code.
>
> It does not provide the functionality for all architectures (only for x64 for now).
What a lot of code.
Why do we want 64-bit futexes?
next prev parent reply other threads:[~2007-03-15 19:08 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 [this message]
2007-03-15 19:12 ` Ulrich Drepper
2007-03-15 19:31 ` Andrew Morton
2007-03-15 19:37 ` Ulrich Drepper
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=20070315110752.f1df4509.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Pierre.Peiffer@bull.net \
--cc=drepper@redhat.com \
--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 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.