mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	mtk.manpages@gmail.com
Subject: Re: [PATCH 3/3] 64-bit futexes: x86 support
Date: Fri, 30 May 2008 20:59:29 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805302056170.3141@woody.linux-foundation.org> (raw)
In-Reply-To: <4840C394.2080807@redhat.com>



On Fri, 30 May 2008, Ulrich Drepper wrote:
> 
> In any case, robbing 64-bit architectures of the possible performance
> gain just because there are ancient versions which cannot do it is just
> plain stupid.  I know you cannot suggest that.

I'm suggesting that there are better approaches than forcing yet another 
new interface onto this thing. As mentioned, the kernel has had 32-bit 
rwsemaphores for a long time. Yes, there is "extra information" outside 
the 32-bit field, but I suspect you simply haven't looked hard enough at 
just using the existing futex code.

You certainly didn't even read - or understand - my emails, since you 
thought I was talking about regular semaphores and ignored the "rw" part 
entirely (not to mention the fact that I talked about reader counts etc, 
which is why I think you didn't even read the email).

		Linus

  reply	other threads:[~2008-05-31  4:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  1:27 Ulrich Drepper
2008-05-31  2:25 ` Linus Torvalds
2008-05-31  3:18   ` Ulrich Drepper
2008-05-31  3:59     ` Linus Torvalds [this message]
2008-05-31  4:25       ` Ulrich Drepper
2008-05-31  4:34         ` Linus Torvalds
2008-05-31  4:45           ` Ulrich Drepper
2008-05-31  7:47             ` David Miller
2008-06-02  8:22 ` Ingo Molnar
2008-06-02 18:43   ` Ingo Molnar

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=alpine.LFD.1.10.0805302056170.3141@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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

all inboxes | Powered by JetHome®