public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: lsscsi-0.07 + scsi host information?
Date: Fri, 14 Feb 2003 08:49:26 -0800	[thread overview]
Message-ID: <20030214084926.B25020@beaverton.ibm.com> (raw)
In-Reply-To: <3E4C1FAE.2090904@torque.net>; from dougg@torque.net on Fri, Feb 14, 2003 at 09:43:58AM +1100

On Fri, Feb 14, 2003 at 09:43:58AM +1100, Douglas Gilbert wrote:

> I would like lsscsi to list SCSI hosts (portals?) but there
> doesn't seem to be enough normalized sysfs information
> available to do that. Is the "/sys/class/scsi-host" sub-tree
> the place to be looking? Of the scsi hosts I have, only
> scsi_debug (thanks to work by Mike Anderson) puts an
> entry in that sub-tree. I would also like to have normalized
> information from the scsi_host structure available (similar
> to what Patrick Mansfield provided for scsi devices).

We could add scsi_host attributes under the same place as the
scsi_host->host_gendev. But with sysfs, you could not tell if they were
pci or scsi_host attributes.

We also need a place in sysfs for scsi core attributes - like
max_scsi_luns, scsi_logging_level, max_scsi_report_luns, and maybe others,
so they can be set and checked via /sysfs. But drivers under sysfs must
(AFAIK) be on a "bus" and bind to devices on that same bus. For scsi core,
we are more like a library, and do not have a specific type and set of
devices to bind to.

-- Patrick Mansfield

      reply	other threads:[~2003-02-14 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 22:43 lsscsi-0.07 + scsi host information? Douglas Gilbert
2003-02-14 16:49 ` Patrick Mansfield [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=20030214084926.B25020@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=dougg@torque.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox