From: Douglas Gilbert <dougg@torque.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Matt Domsch <Matt_Domsch@Dell.com>
Subject: Re: [RFC][PATCH] adding PCI bus information to SCSI layer
Date: Sat, 14 Apr 2001 12:27:41 -0400 [thread overview]
Message-ID: <3AD87A7D.BB66C5DA@torque.net> (raw)
In-Reply-To: <E14oBtM-0003fN-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Also ISA adapters are not the only non-PCI adapters,
> > there are the growing band of pseudo adapters that
> > may or may not have a PCI bus at the bottom of some
> > other protocol stack.
>
> An ioctl might be better. We already have an ioctl for querying the lun
> information for a disk. We could also return the bus information for its
> controller(s) [remember multipathing]
Both 'cat /proc/scsi/scsi' and ioctls used on
fds belonging to the existing upper level drivers
(e.g. sd and sr) have a problem as far as getting
HBA environment information: there needs to be at
least one SCSI device (target) connected to the
HBA. With no SCSI devices connected, there is no
fd to do an ioctl on. [The same problem arises
if a device is there but marked offline, has an
exclusive lock on it, ...]
Perhaps Matt could look at the approach I have taken
with the scsimon experimental upper level driver.
Scsimon was originally designed to get scsi based
information to the /sbin/hotplug mechanism. It also
supplies ioctls to probe HBAs as well as SCSI devices.
More information about it can be found at:
http://www.torque.net/scsi/scsimon.html
It should not be difficult to add HBA PCI bus information
to scsimon (after the Scsi_Host structure is expanded to
hold that information).
Doug Gilbert
next prev parent reply other threads:[~2001-04-14 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 22:07 [RFC][PATCH] adding PCI bus information to SCSI layer Douglas Gilbert
2001-04-13 22:18 ` Alan Cox
2001-04-14 16:27 ` Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 1:58 Matt_Domsch
2001-04-24 2:14 ` Jeff Garzik
2001-04-23 22:06 Matt_Domsch
2001-04-23 22:27 ` Jeff Garzik
2001-04-23 23:04 ` Alan Cox
2001-04-24 3:32 ` Douglas Gilbert
2001-04-13 22:31 Matt_Domsch
2001-04-13 21:34 Matt Domsch
2001-04-14 7:35 ` Jonathan Lundell
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=3AD87A7D.BB66C5DA@torque.net \
--to=dougg@torque.net \
--cc=Matt_Domsch@Dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.