All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Martin Hicks <mort@wildopensource.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exporting physical topology information
Date: Thu, 18 Mar 2004 15:21:39 -0800	[thread overview]
Message-ID: <20040318232139.GA17586@kroah.com> (raw)
In-Reply-To: <20040317213714.GD23195@localhost>

On Wed, Mar 17, 2004 at 04:37:14PM -0500, Martin Hicks wrote:
> 
> Hi,
> 
> I'm trying to figure out what the best way is to export a minimal amount
> of physical topology information to userland.  Would it be acceptable to
> export this kind of information with sysfs?
> 
> I'm not proposing that we build an entire physical topology tree in
> sysfs, but just providing an attribute file.  The two most obvious
> examples of where this would be useful is for nodes and pci busses.  The
> Altix platform is a modular system with CPU bricks and IO bricks.  We
> currently have no method for locating where "node0" is, nor do we have a
> method for locating pci bus 0000:20, for example.
> 
> If we could physically locate a PCI bus, then it would be much easier
> to (for example) locate our defective SCSI disk that is target4 on the
> SCSI controller that is on pci bus 0000:20.

Um, what's wrong with the current /sys/class/pci_bus/*/cpuaffinity files
for determining this topology information?  That is why it was added.

thanks,

greg k-h

  parent reply	other threads:[~2004-03-19  0:18 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 [this message]
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

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=20040318232139.GA17586@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mort@wildopensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.