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 22:46:46 +0000 [thread overview]
Message-ID: <16927.43734.546795.91007@napali.hpl.hp.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB7506494303077707@scsmsx401.amr.corp.intel.com>
>>>>> On Fri, 25 Feb 2005 13:15:05 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> For pinning a task (or set of tasks) to same core or multiple
Rohit> cores, you only need package id and core id. The thread
Rohit> information is really not required. Right?
Yeah, that's true. At least I can't come up with a good reason of
wanting to know which thread exactly you're running on. Having said
that, from a user-perspective, looking at two entries in /proc/cpuinfo
and seeing that the socket id/core id are the same and only the thread
ids are different probably would give me more of a warm and fuzzy
feeling.
Rohit> AFAIK, an easy way for apps (for licensing etc.) to find out
Rohit> if and how many LEUs are present without doing any other
Rohit> calculation.
Yeah, I guess "MAX(thread_id) + 1" does count as a "calculation". And
I thought computers where good at that... ;-)
--david
next prev parent reply other threads:[~2005-02-25 22:46 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
2005-02-25 20:47 ` Seth, Rohit
2005-02-25 21:15 ` Seth, Rohit
2005-02-25 22:46 ` David Mosberger [this message]
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.43734.546795.91007@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