From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch]:MC/MT enabling/identification for IA-64
Date: Fri, 25 Feb 2005 20:47:15 +0000 [thread overview]
Message-ID: <16927.36563.804160.355113@napali.hpl.hp.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB7506494303077707@scsmsx401.amr.corp.intel.com>
>>>>> On Fri, 25 Feb 2005 12:12:34 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> "Cpu Cores" identifying the number of cores in a physical
Rohit> package is present in x86_64 and not there in i386 tree.
Rohit> Will following work:
Rohit> Physical id: Identifying the unique physical package id for LEU
Rohit> Core id: Identifying the unique core id on that specific physical
Rohit> package
Rohit> Siblings: Identifying the total number LEUs on that physical package.
Well, I think it would be useful if we can look at /proc/cpuinfo and
get a mapping from Linux CPU number to "topological address" (socket
id, core id, thread id). With that plus taskset, it would be very
easy to run a test with, for example, two processes pinned to the two
threads on the same core or pinned to separate cores, etc.
Rohit> Siblings is the one that apps have already started using on i386.
What is it being used for?
--david
next prev parent reply other threads:[~2005-02-25 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 19:19 [patch]:MC/MT enabling/identification for IA-64 Seth, Rohit
2005-02-18 23:41 ` David Mosberger
2005-02-22 18:24 ` Seth, Rohit
2005-02-25 1:27 ` David Mosberger
2005-02-25 2:22 ` Seth, Rohit
2005-02-25 6:11 ` David Mosberger
2005-02-25 20:12 ` Seth, Rohit
2005-02-25 20:27 ` Ashok Raj
2005-02-25 20:47 ` David Mosberger [this message]
2005-02-25 20:47 ` Seth, Rohit
2005-02-25 21:15 ` Seth, Rohit
2005-02-25 22:46 ` David Mosberger
2005-02-25 23:01 ` Seth, Rohit
2005-02-25 23:03 ` David Mosberger
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=16927.36563.804160.355113@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox