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 21:34:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805302129240.3141@woody.linux-foundation.org> (raw)
In-Reply-To: <4840D335.6040406@redhat.com>



On Fri, 30 May 2008, Ulrich Drepper wrote:
> 
> I guess have to expect to expect to be insulted by you.

Guess why? What comes around goes around. 

You just dismissed (without apparently even understanding them) my 
concerns about a patch that comes out of the blue, when I ask whether you 
really looked into trying to do it other ways.

You didn't even post the code that would _use_ this. You just blindly 
claim that you're the only one who can know things like this and can do 
serialization, and that your way is the only approach.

Color me not impressed. 

I did not insult you until you didn't even understand my first email. We 
have had an efficient 32-bit rwlock in the kernel for a long time. So I 
(quite naturally) questioned your statement (that had no backing up 
what-so-ever) that it cannot be done.

Sure, futex use and user space is not the same as the kernel code. It's 
possible that you really do need 64-bit futexes. But quite frankly, the 
only thing you have proven so far is that you're an ass.

			Linus

  reply	other threads:[~2008-05-31  4:35 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
2008-05-31  4:25       ` Ulrich Drepper
2008-05-31  4:34         ` Linus Torvalds [this message]
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.0805302129240.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®