From: Andi Kleen <ak@suse.de>
To: "Zhang, Yanmin" <yanmin.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org, "Pallipadi,
Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [discuss] [PATCH] Export cpu topology for IA32 and x86_64 by sysfs
Date: Wed, 14 Dec 2005 04:51:11 +0100 [thread overview]
Message-ID: <20051214035111.GF15804@wotan.suse.de> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E840431BB03@pdsmsx404>
On Wed, Dec 14, 2005 at 11:11:00AM +0800, Zhang, Yanmin wrote:
> The patch exports the cpu topology info through sysfs on ia32/x86_64
> machines. The info is similar to /proc/cpuinfo.
>
> The exported items are:
> /sys/devices/system/cpu/cpuX/topology/physical_package_id(representing
> the physical package id of cpu X)
> /sys/devices/system/cpu/cpuX/topology/core_id (representing the cpu core
> id to cpu X)
> /sys/devices/system/cpu/cpuX/topology/thread_siblings (representing the
> thread siblings to cpu X)
> /sys/devices/system/cpu/cpuX/topology/core_siblings (represeting the
> core siblings to cpu X)
Hmm, I'm not sure it is that useful. Did someone decide to move
all information from cpuinfo into sysfs?
And if it's done I think it needs Documentation somewhere.
Anyways, the notifier is wrong. You need to handle CPU_UP_CANCELLED
too.
And you could probably shrink the code size of the show function
in half by switching data instead of functions.
-Andi
next prev parent reply other threads:[~2005-12-14 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 3:11 Zhang, Yanmin
2005-12-14 3:51 ` Andi Kleen [this message]
2005-12-14 5:38 [discuss] " Zhang, Yanmin
2005-12-15 1:39 Pallipadi, Venkatesh
2005-12-15 3:37 ` Andi Kleen
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=20051214035111.GF15804@wotan.suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=yanmin.zhang@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
Powered by JetHome