From: David Miller <davem@davemloft.net>
To: clameter@sgi.com
Cc: ak@suse.de, linux-kernel@vger.kernel.org, travis@sgi.com,
jeremy@goop.org
Subject: Re: x86: Convert cpu_core_map to be a per cpu variable
Date: Fri, 13 Jul 2007 15:41:19 -0700 (PDT) [thread overview]
Message-ID: <20070713.154119.15263594.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707130933140.21777@schroedinger.engr.sgi.com>
From: Christoph Lameter <clameter@sgi.com>
Date: Fri, 13 Jul 2007 09:34:02 -0700 (PDT)
> But the code modified here is x86_64 and i386 specific? Is there an
> overlap?
I see, the acessor is abstracted via a function.
That seems pointless, and allows you to do things like this, improving
the implementation on one set of platforms yet leave others using
SMT/multi-core scheduling behind.
It makes a lot more sense to make the implementation consistent
and therefore the improvements are seen on every platform.
next prev parent reply other threads:[~2007-07-13 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 6:58 Christoph Lameter
2007-07-13 7:08 ` David Miller
2007-07-13 16:34 ` Christoph Lameter
2007-07-13 22:41 ` David Miller [this message]
2007-07-13 22:50 ` Christoph Lameter
2007-07-13 22:51 ` David Miller
2007-07-13 13:49 ` Jeremy Fitzhardinge
2007-07-17 19:27 ` Siddha, Suresh B
2007-07-23 19:34 ` Christoph Lameter
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=20070713.154119.15263594.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=travis@sgi.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®