From: Nathan Lynch <ntl@pobox.com>
To: "Zhang, Yanmin" <yanmin.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, "Pallipadi,
Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH 1/2] Export cpu info by sysfs
Date: Tue, 13 Dec 2005 23:14:20 -0500 [thread overview]
Message-ID: <20051214041419.GA3475@localhost.localdomain> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E840431BB3B@pdsmsx404>
Hello-
Zhang, Yanmin wrote:
> I worked out 2 patches to export cpu topology and cache info by sysfs.
>
> The first patch is to export cpu topology info including below items
> (attributes) which are similar to /proc/cpuinfo.
>
> /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_id (representing the cpu
> thread 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)
I haven't looked at the patches in detail, but I have a concern about
this approach. How is it that making new architecture-specific
attributes under cpu directories in sysfs is preferable to the already
architecture-specific format of /proc/cpuinfo and other proc entries?
If we're going to create a new user interface for exposing system
topology (cores and threads etc), I would like for it to be as
architecture-neutral as possible. We already do this for numa, for
example.
Nathan
next prev parent reply other threads:[~2005-12-14 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 3:30 [PATCH 1/2] Export cpu info by sysfs Zhang, Yanmin
2005-12-14 4:14 ` Nathan Lynch [this message]
2005-12-14 10:12 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 1:33 Zhang, Yanmin
2005-12-15 2:03 ` Paul Jackson
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=20051214041419.GA3475@localhost.localdomain \
--to=ntl@pobox.com \
--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