From: Jesse Barnes <jbarnes@sgi.com>
To: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: Exporting physical topology information
Date: Fri, 19 Mar 2004 09:51:52 -0800 [thread overview]
Message-ID: <200403190951.52899.jbarnes@sgi.com> (raw)
In-Reply-To: <20040318232139.GA17586@kroah.com>
On Thursday 18 March 2004 3:21 pm, Greg KH wrote:
> > 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.
Nothing, except that it only provides logical information. In a large
system, it's really useful to be able to physically locate a component
somehow. That was the idea behind adding 'physid'. For example:
[jbarnes@spamtin pci0000:02]$ pwd
/sys/devices/pci0000:02
[jbarnes@spamtin pci0000:02]$ cat physid
rack: 5
module: 12
slot: 3
or for nodes:
[jbarnes@spamtin node2]$ cat physid
rack: 1
module: 3
slot: 1
Then you could walk into the lab and know exactly which device to
kick. Obviously, these values would be platform specific, though on
ia64 and some x86 platforms, we could probably use the ACPI namespace
to access some of the info, and on ppc the OF namespace might have it.
Thanks,
Jesse
next prev parent reply other threads:[~2004-03-19 17:52 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 [this message]
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=200403190951.52899.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=greg@kroah.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