mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	linux-kernel@vger.kernel.org, akpm@osdl.org,
	rohit.seth@intel.com
Subject: Re: [Patch] x86, x86_64: Intel dual-core detection
Date: Wed, 16 Mar 2005 10:22:40 -0800	[thread overview]
Message-ID: <20050316102239.A10250@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050316170412.GA51070@muc.de>; from ak@muc.de on Wed, Mar 16, 2005 at 06:04:12PM +0100

On Wed, Mar 16, 2005 at 06:04:12PM +0100, Andi Kleen wrote:
> On Tue, Mar 15, 2005 at 05:36:25PM -0800, Siddha, Suresh B wrote:
> > It adds two new fields "core id" and "cpu cores" to x86 /proc/cpuinfo
> > and the "core id" field for x86_64("cpu cores" field is already present in
> > x86_64).
> 
> Thanks. I have a similar patch for AMD CPUs, unfortuntely it uses 
> different names ("shared cores" etc.)

2.6.11 already has "cpu cores" for x86_64. I would like to retain that.

> > 
> > This patch also adds cpu_core_map similar to cpu_sibling_map.
> Called cpu_sharecore_map in my patch.

cpu_sharecore_map sounds like HT logical siblings sharing the core. Initially 
I was calling it as cpu_coresibling_map but later thought cpu_core_map is 
a smaller name.

> 
> Hmm, which names should be chosen?

For /proc/cpuinfo, I want to stick with "cpu cores" and "core id"
But I am open for kernel variable names.

Depending on what we decide on kernel variable names, I will see if I have 
to make any changes to the IPF patch we posted last week.

thanks,
suresh

      reply	other threads:[~2005-03-16 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16  1:36 Siddha, Suresh B
2005-03-16 17:04 ` Andi Kleen
2005-03-16 18:22   ` Siddha, Suresh B [this message]

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=20050316102239.A10250@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rohit.seth@intel.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®