mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Andi Kleen <ak@suse.de>, "Zhang, Yanmin" <yanmin.zhang@intel.com>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org,
	Nathan Lynch <ntl@pobox.com>
Subject: Re: [discuss] [PATCH] Export cpu topology for IA32 and x86_64 by sysfs
Date: Thu, 15 Dec 2005 04:37:09 +0100	[thread overview]
Message-ID: <20051215033709.GS23384@wotan.suse.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6006A22399@scsmsx403.amr.corp.intel.com>

> Not really. The current display in /proc/cpuinfo, though useful for
> human reader,
> is not very friendly to scripts. And if one wants to find out which
> logical CPUs belong
> to the same core, there will have to be some amount of code in userlevel
> to parse
> the /proc/cpuinfo and get this info. So, we thought that it may be
> useful to 
> export the masks to the user directly in a genric way. And, while doing
> that
> thinking was adding new fields in /sysfs rather than /proc/ was better.

Hmm - having written both /proc and /sys parsers i'm not sure your new
setup will be any easier to handle in a program than /proc/cpuinfo. Probably not.

I would suggest you supply a standard C library and command line utility
at least - but at least for the later the output would
be likely not that different from cat /proc/cpuinfo

> Having said that, I feel Nathan's suggestion of doing it in more
> architecturally-neutral way should be better than this. We will have a
> relook at this one now.

That makes sense. /proc/cpuinfo is not that bad in itself, except that
it's very architecture dependent.

-Andi


  reply	other threads:[~2005-12-15  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15  1:39 Pallipadi, Venkatesh
2005-12-15  3:37 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-14  5:38 Zhang, Yanmin
2005-12-14  3:11 Zhang, Yanmin
2005-12-14  3:51 ` [discuss] " 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=20051215033709.GS23384@wotan.suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntl@pobox.com \
    --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