All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Avi Kivity <avi@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	benh@kernel.crashing.org, akpm@linux-foundation.org,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] lib: Provide generic atomic64_t implementation
Date: Sun, 14 Jun 2009 19:44:45 -0700	[thread overview]
Message-ID: <ada4ouixlk2.fsf@cisco.com> (raw)
In-Reply-To: <4A34F564.2010500@redhat.com> (Avi Kivity's message of "Sun, 14 Jun 2009 16:04:36 +0300")


 > The new Nehalems provide 8 logical threads in a single socket.  All
 > those threads share a cache, and they have cmpxchg8b anyway, so this
 > won't matter.

FWIW, Nehalem EX actually goes to 8 cores/16 threads per socket.  But
worrying about 32-bit performance on Nehalem is a little silly -- this
simplest solution is simply to run a 64-bit kernel.

 - R.

WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <rdreier@cisco.com>
To: Avi Kivity <avi@redhat.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Paul Mackerras <paulus@samba.org>,
	akpm@linux-foundation.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] lib: Provide generic atomic64_t implementation
Date: Sun, 14 Jun 2009 19:44:45 -0700	[thread overview]
Message-ID: <ada4ouixlk2.fsf@cisco.com> (raw)
In-Reply-To: <4A34F564.2010500@redhat.com> (Avi Kivity's message of "Sun, 14 Jun 2009 16:04:36 +0300")


 > The new Nehalems provide 8 logical threads in a single socket.  All
 > those threads share a cache, and they have cmpxchg8b anyway, so this
 > won't matter.

FWIW, Nehalem EX actually goes to 8 cores/16 threads per socket.  But
worrying about 32-bit performance on Nehalem is a little silly -- this
simplest solution is simply to run a 64-bit kernel.

 - R.

  reply	other threads:[~2009-06-15  2:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  7:10 [PATCH 1/2] lib: Provide generic atomic64_t implementation Paul Mackerras
2009-06-13  7:10 ` Paul Mackerras
2009-06-13 20:13 ` Linus Torvalds
2009-06-13 20:13   ` Linus Torvalds
2009-06-13 20:25   ` Linus Torvalds
2009-06-13 20:25     ` Linus Torvalds
2009-06-13 20:56     ` Ingo Molnar
2009-06-13 20:56       ` Ingo Molnar
2009-06-14 11:53     ` Avi Kivity
2009-06-14 11:53       ` Avi Kivity
2009-06-14 12:21       ` Paul Mackerras
2009-06-14 12:21         ` Paul Mackerras
2009-06-14 13:04         ` Avi Kivity
2009-06-14 13:04           ` Avi Kivity
2009-06-15  2:44           ` Roland Dreier [this message]
2009-06-15  2:44             ` Roland Dreier
2009-06-15  4:30             ` Paul Mackerras
2009-06-15  4:30               ` Paul Mackerras
2009-06-16 22:27           ` Gabriel Paubert
2009-06-16 22:27             ` Gabriel Paubert
2009-06-13 21:53 ` Arnd Bergmann
2009-06-13 21:53   ` Arnd Bergmann
2009-06-18 23:55 ` Mike Frysinger
2009-06-18 23:55   ` Mike Frysinger
2009-06-19  0:46   ` Benjamin Herrenschmidt
2009-06-19  0:46     ` Benjamin Herrenschmidt
2009-06-19  0:47   ` Paul Mackerras
2009-06-19  0:47     ` Paul Mackerras
2009-06-19  0:49     ` Mike Frysinger
2009-06-19  0:49       ` Mike Frysinger

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=ada4ouixlk2.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --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.