public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	"Dinakar Guniguntala" <dino@in.ibm.com>,
	"Jean-Pierre Dion" <jean-pierre.dion@bull.net>,
	"Sébastien Dugué" <sebastien.dugue@bull.net>,
	"Darren Hart" <dvhltc@us.ibm.com>
Subject: Re: [PATCH 2.6.19.1-rt15][RFC] - futex_requeue_pi implementation (requeue from futex1 to PI-futex2)
Date: Thu, 04 Jan 2007 00:08:35 -0800	[thread overview]
Message-ID: <459CB603.9010208@redhat.com> (raw)
In-Reply-To: <459CB3E6.9080906@bull.net>

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

Pierre Peiffer wrote:
> But, just for information, what is the sys_futex64 for, exactly ? Is
> there a plan to have in the future a 64-bit PID ?

This has nothing to do with PIDs.  We need 64-bit values for more
complex bit fields which can then be stored in the futex.  One example
is a new, much faster rwlock implementation.  These are not practical
without 64-bit futexes.  This is why I asked Ingo to add the code.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

      reply	other threads:[~2007-01-04  8:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 12:32 [PATCH 2.6.19.1-rt15][RFC] - futex_requeue_pi implementation (requeue from futex1 to PI-futex2) Pierre Peiffer
2007-01-03 12:35 ` Ingo Molnar
2007-01-03 14:35   ` Pierre Peiffer
2007-01-03 15:56     ` Ingo Molnar
2007-01-04  7:59       ` Pierre Peiffer
2007-01-04  8:08         ` 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=459CB603.9010208@redhat.com \
    --to=drepper@redhat.com \
    --cc=dino@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pierre.peiffer@bull.net \
    --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