From: Douglas Gilbert <dougg@torque.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: lsscsi-0.09
Date: Fri, 04 Apr 2003 22:55:45 +1000 [thread overview]
Message-ID: <3E8D80D1.9070902@torque.net> (raw)
In-Reply-To: 20030404124617.A24518@infradead.org
Christoph Hellwig wrote:
> On Fri, Apr 04, 2003 at 03:51:50PM +1000, Douglas Gilbert wrote:
>
>>lsscsi is a utility the uses sysfs in kernels >= lk 2.5.50
>>to list information about all SCSI devices (including devices
>>that use the SCSI stack such as USB mass storage devices)
>>and SCSI hosts. Both a compact format (default), one line
>>per device, and a "classic" format (like the output of
>>'cat /proc/scsi/scsi') are supported for devices.
>
>
> That reminds me that I wanted to get rid of /proc/scsi/scsi eventually.
> Does someone have an idea for a replacement of it's write routine?
> Some of them don't fit nicely into the sysfs model unfortunatley.
Christoph,
The scsi mid level is just another driver (singleton device?)
so it can have driver parameters in sysfs. If sysfs is going to
displace writes to /proc/scsi/scsi then some of its rules may
have to bend (if they haven't already been). The "one parameter
one file node" rule would make for an ugly replacement of:
# echo "scsi add-single-device 1 2 3 4" > /proc/scsi/scsi
Actually, scsi_debug's sysfs interface is not far away from
doing something like that (adding hosts rather than individual
devices) but I'm not sure the syntax is very clear:
# echo 3 > num_tgts
# echo 64 > max_luns
# echo 2 > add_host # add 2 hosts, each with 3 targets,
# each with 64 luns
# echo -1 > add_hosts # remove highest numbered host
Doug Gilbert
next prev parent reply other threads:[~2003-04-04 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 5:51 lsscsi-0.09 Douglas Gilbert
2003-04-04 11:46 ` lsscsi-0.09 Christoph Hellwig
2003-04-04 12:55 ` Douglas Gilbert [this message]
2003-04-04 13:03 ` lsscsi-0.09 Christoph Hellwig
2003-04-04 18:48 ` lsscsi-0.09 Patrick Mansfield
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=3E8D80D1.9070902@torque.net \
--to=dougg@torque.net \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox