From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Patch] sched: new sched domain for representing multi-core
Date: Fri, 10 Feb 2006 16:51:27 -0800 [thread overview]
Message-ID: <20060210165127.A28881@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060209095929.GZ4215@implementation.labri.fr>; from samuel.thibault@ens-lyon.org on Thu, Feb 09, 2006 at 10:59:29AM +0100
On Thu, Feb 09, 2006 at 10:59:29AM +0100, Samuel Thibault wrote:
> Hi,
>
> Could cache-sharing multi-core chips be represented somehow in
> /proc/cpuinfo too? Such information can be useful in userspace too
> (without having to run cpuid & such). For instance:
>
> physical id : 0
> siblings : 2
> l3 id : 0
> l2 id : 0
> core id : 0
> cpu cores : 2
>
> etc.
/sys/devices/system/cpu/cpuX/cache/indexY/shared_cpu_map has this info
already
There is one more patch in works which enables exporting the multi-core
topology through sysfs
http://www.ussg.iu.edu/hypermail/linux/kernel/0601.3/0275.html
thanks,
suresh
next prev parent reply other threads:[~2006-02-11 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 9:59 [Patch] sched: new sched domain for representing multi-core Samuel Thibault
2006-02-11 0:51 ` Siddha, Suresh B [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 9:51 Siddha, Suresh B
2006-01-27 0:08 ` Ingo Molnar
2006-01-27 3:51 ` Siddha, Suresh B
2006-01-28 0:00 ` Andrew Morton
2006-01-31 1:28 ` Siddha, Suresh B
2006-02-01 1:12 ` Andrew Morton
2006-02-01 1:48 ` Siddha, Suresh B
2006-02-01 2:21 ` Andrew Morton
2006-02-01 2:52 ` Siddha, Suresh B
2006-01-27 4:42 ` Andi Kleen
2006-01-28 1:45 ` Siddha, Suresh B
2006-01-29 16:56 ` Pavel Machek
2006-01-31 1:31 ` Siddha, Suresh B
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=20060210165127.A28881@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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;
as well as URLs for NNTP newsgroup(s).