From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exporting physical topology information
Date: Fri, 7 May 2004 15:38:22 -0700 [thread overview]
Message-ID: <20040507223822.GJ14660@kroah.com> (raw)
In-Reply-To: <200405071313.43493.jbarnes@engr.sgi.com>
On Fri, May 07, 2004 at 01:13:43PM -0700, Jesse Barnes wrote:
> On Friday, March 19, 2004 10:53 am, Jesse Barnes wrote:
> > Here's the (very platform specific) patch I did for Altix, just to see
> > what it would look like, and to solicit comments. There's some other
> > per-node stuff that would be nice to have available to userspace too,
> > mostly for administrative purposes, like the chipset revision and
> > type, firmware revision, and other hardware specific details. One way
> > to export that sort of thing is with some sort of arbitrary data blob,
> > but like you said, that violates the sysfs one file, one value
> > principle.
>
> Greg, any comments on this? (Sorry I was gone for much of last month and lost
> track of this thread.) Maybe a whole subdirectory containing physical tag,
> version files and such would make more sense?
I think my main comments was you should work with the other numa people
so that you all agree on one common format to export this data in sysfs.
If you all agree that this is the way to do it, I'll accept the patch :)
thanks,
greg k-h
prev parent reply other threads:[~2004-05-08 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 21:37 Exporting physical topology information Martin Hicks
2004-03-18 17:44 ` Jesse Barnes
2004-03-18 23:21 ` Greg KH
2004-03-19 17:48 ` Martin Hicks
2004-03-19 17:57 ` Greg KH
2004-03-19 17:51 ` Jesse Barnes
2004-03-19 17:59 ` Greg KH
2004-03-19 18:53 ` Jesse Barnes
2004-05-07 20:13 ` Jesse Barnes
2004-05-07 22:38 ` Greg KH [this message]
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=20040507223822.GJ14660@kroah.com \
--to=greg@kroah.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@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