From: Jonathan Lundell <jlundell@pobox.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: Thu, 26 Apr 2001 22:24:52 -0700 [thread overview]
Message-ID: <p05100303b70eadd613b0@[207.213.214.37]> (raw)
In-Reply-To: <200104270431.f3R4V4630593@vindaloo.ras.ucalgary.ca>
In-Reply-To: <CDF99E351003D311A8B0009027457F140810E286@ausxmrr501.us.dell.com> <200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca> <p05100313b70bb73ce962@[207.213.214.37]> <200104270431.f3R4V4630593@vindaloo.ras.ucalgary.ca>
At 10:31 PM -0600 2001-04-26, Richard Gooch wrote:
>BTW: please fix your mailer to do linewrap at 72 characters. Your
>lines are hundreds of characters long, and that's hard to read.
Sorry for the inconvenience. There are a lot of reasons why I believe
it's properly a display function to wrap long lines, and that an MUA
has no business altering outgoing messages (one on-topic reason being
that patches get screwed up by inserted newlines), but I grant that
there are broken clients out there that can't or won't or don't wrap
at display time.
On the subject of the Subject, Jeff Garzik recently (21 March)
suggested adding geographic information to the ethtool interface,
pci_dev->slot_name in the case of a PCI-based interface. There's
something to be said for having a uniform method of identifying the
location of devices, or at least a uniform parsable format. (A
potential shortcoming of Jeff's scheme, perhaps, is that it needs to
identify the slot_name as a PCI slot_name, though I could be missing
something there.)
Consider, instead of /dev/bus/pci0/dev1/fcn0/bus0/tgt1/lun2/part3
something like
/dev/bus/pci0d1f0/scsi0t1l2p3
or
/dev/bus/pci0:d1:f0/scsi0:t1:l2:p3
Are there systems with more than one PCI bus numbering domain? I
don't see why not, in principle (not an issue for SCSI, which doesn't
have bus numbering). So perhaps:
/dev/bus/pci0:b0:d1:f0/scsi0:t1:l2:p3
which distinguishes between PCI domains and PCI bus numbers.
At 10:31 PM -0600 2001-04-26, Richard Gooch wrote:
>Sure. I haven't made a decision on the names yet. I was just sketching
>out the idea.
It's a good idea. Just feedback on the initial sketch.
A related idea would be the ability to translate from a logical PCI
slot number, as above, and a physically meaningful description that
the user could use to identify an actual slot. Unfortunately the
proper place for such a translation function is in the
(hardware-specific) BIOS.
--
/Jonathan Lundell.
next prev parent reply other threads:[~2001-04-27 5:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch
2001-04-27 4:31 ` Richard Gooch
2001-05-01 1:27 ` Richard Gooch
2001-05-01 8:46 ` Ingo Oeser
2001-05-01 16:53 ` Richard Gooch
2001-05-01 20:32 ` Alan Cox
2001-05-02 15:03 ` Ingo Oeser
2001-05-02 15:54 ` Alan Cox
2001-05-03 8:57 ` Chris Wedgwood
2001-05-03 9:49 ` Alan Cox
2001-05-03 10:23 ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell
2001-04-27 5:24 ` Jonathan Lundell [this message]
2001-05-01 14:38 ` Jonathan Lundell
2001-05-03 7:32 ` Kai Henningsen
2001-05-03 7:51 ` Jonathan Lundell
2001-05-11 16:32 ` Ralf Baechle
2001-05-11 23:00 ` Steven Willoughby
2001-05-11 22:49 ` Jonathan Lundell
2001-05-12 2:20 ` Ralf Baechle
2001-05-12 4:21 ` Jonathan Lundell
[not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen
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='p05100303b70eadd613b0@[207.213.214.37]' \
--to=jlundell@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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
all inboxes | Powered by JetHome®