All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <npiggin@suse.de>
Cc: David Howells <dhowells@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <ak@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch] generic rwsems
Date: Fri, 13 Apr 2007 06:22:00 -0700	[thread overview]
Message-ID: <20070413132200.GT2986@holomorphy.com> (raw)
In-Reply-To: <20070413124303.GD966@wotan.suse.de>

On Fri, Apr 13, 2007 at 02:43:03PM +0200, Nick Piggin wrote:
> Yes, this is the case on our 2 premiere SMP powerhouse architectures,
> sparc32 and parsic.

sparc32 is ultra-legacy and I have a tremendous amount of work to do on
SMP there. I don't feel that efficiency of locking primitives is a
crucial issue for sparc32.


-- wli

WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <npiggin@suse.de>
Cc: David Howells <dhowells@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <ak@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch] generic rwsems
Date: Fri, 13 Apr 2007 06:22:00 -0700	[thread overview]
Message-ID: <20070413132200.GT2986@holomorphy.com> (raw)
In-Reply-To: <20070413124303.GD966@wotan.suse.de>

On Fri, Apr 13, 2007 at 02:43:03PM +0200, Nick Piggin wrote:
> Yes, this is the case on our 2 premiere SMP powerhouse architectures,
> sparc32 and parsic.

sparc32 is ultra-legacy and I have a tremendous amount of work to do on
SMP there. I don't feel that efficiency of locking primitives is a
crucial issue for sparc32.


-- wli

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-04-13 13:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 10:04 [patch] generic rwsems Nick Piggin
2007-04-13 10:04 ` Nick Piggin
2007-04-13 10:19 ` fastcalls, was " Christoph Hellwig
2007-04-13 10:59   ` Nick Piggin
2007-04-13 10:25 ` Nick Piggin
2007-04-13 10:25   ` Nick Piggin
2007-04-13 11:44   ` David Howells
2007-04-13 11:44     ` David Howells
2007-04-13 12:13     ` Christoph Hellwig
2007-04-13 12:13       ` Christoph Hellwig
2007-04-13 10:53 ` Andi Kleen
2007-04-13 10:53   ` Andi Kleen
2007-04-13 11:20   ` Nick Piggin
2007-04-13 11:20     ` Nick Piggin
2007-04-13 12:09 ` David Howells
2007-04-13 12:09   ` David Howells
2007-04-13 12:43   ` Nick Piggin
2007-04-13 12:43     ` Nick Piggin
2007-04-13 13:22     ` William Lee Irwin III [this message]
2007-04-13 13:22       ` William Lee Irwin III
2007-04-13 13:31     ` David Howells
2007-04-13 13:31       ` David Howells
2007-04-13 14:03       ` Nick Piggin
2007-04-13 14:03         ` Nick Piggin
2007-04-13 14:29       ` Eric Dumazet
2007-04-13 14:29         ` Eric Dumazet
2007-04-13 14:49         ` David Howells
2007-04-13 14:49           ` David Howells

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=20070413132200.GT2986@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=torvalds@linux-foundation.org \
    /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.