From: Douglas Gilbert <dougg@torque.net>
To: Mike Anderson <andmike@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] scsi host sysfs support again [0/4]
Date: Tue, 06 May 2003 11:12:27 +1000 [thread overview]
Message-ID: <3EB70BFB.8080009@torque.net> (raw)
In-Reply-To: <20030505214532.GB3254@beaverton.ibm.com>
Mike Anderson wrote:
> Douglas Gilbert [dougg@torque.net] wrote:
>
>>What seems to be missing, at least in what I am
>>running here is a useful 'name'. There is no 'name'
>>file in the listing above (under each 'host<n>'
>>directory). There is a 'name' file in that 'device' (symlink)
>>directory but it is an empty file here.
>>
>>
>>># tree /sys/bus/scsi/devices
>>>/sys/bus/scsi/devices
>>>|-- 0:0:0:0 -> ../../../devices/pci0/00:09.0/host0/0:0:0:0
>>
>>So finally I can get some output from my
>>version of lsscsi (unreleased version 10):
>>
>>$ lsscsi -Hl
>>[0] ??
>> cmd_per_lun=64 host_busy=0 sg_tablesize=96 unchecked_isa_dma=0
>>[1] ??
>> cmd_per_lun=64 host_busy=0 sg_tablesize=96 unchecked_isa_dma=0
>>[2] ??
>> cmd_per_lun=3 host_busy=0 sg_tablesize=64 unchecked_isa_dma=0
>>[3] ??
>> cmd_per_lun=5 host_busy=0 sg_tablesize=255 unchecked_isa_dma=0
>>
>>Hosts 0 and 1 are the 2 HBAs on a Tekram 390u3w while
>>host 2 is a scsi_debug pseudo host and host3 is
>>ide-scsi. A name would be instructive.
>>
>>$ lsscsi
>>[0:0:1:0] disk FUJITSU MAM3184MP 0106 /dev/sda
>>[2:0:0:0] disk Linux scsi_debug 0004 /dev/sdb
>>[3:0:0:0] cd CREATIVE CD5233E 1.00 /dev/sr0
>>
>
>
> OK, that is a bug. Is proc_name ok for name
>
> # cat /sys/class/scsi_host/*/device/name
> ips
> aic7xxx
> aic7xxx
Mike,
Yes, proc_name is fine (although the previous release
of this patch set used a longer winded variant).
Also the 'unique_id' attribute looks a bit strange
(or is aften misued by LLDs).
$ cat /sys/class/scsi_host/host[0123]/unique_id
33792 # half 390u3w
32768 # other half 390u3w
0 # ide-scsi
0 # Adaptec AIC-7892A
This is nothing to do with your patch, of course. Does
the unique_id help the user space in any way?
Doug Gilbert
next prev parent reply other threads:[~2003-05-06 0:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 8:33 [RFC] scsi host sysfs support again [0/4] Mike Anderson
2003-05-05 8:34 ` [RFC] scsi host sysfs support again [1/4] Mike Anderson
2003-05-05 8:35 ` [RFC] scsi host sysfs support again [2/4] Mike Anderson
2003-05-05 8:37 ` [RFC] scsi host sysfs support again [3/4] Mike Anderson
2003-05-05 8:38 ` [RFC] scsi host sysfs support again [4/4] Mike Anderson
2003-05-05 8:38 ` [RFC] scsi host sysfs support again [0/4] Christoph Hellwig
2003-05-05 9:40 ` Douglas Gilbert
2003-05-05 10:00 ` Mike Anderson
2003-05-05 9:48 ` Mike Anderson
2003-05-05 10:17 ` Christoph Hellwig
2003-05-06 1:05 ` Mike Anderson
2003-05-07 15:44 ` Christoph Hellwig
2003-05-07 16:15 ` Mike Anderson
2003-05-07 16:41 ` Christoph Hellwig
2003-05-05 11:46 ` Douglas Gilbert
2003-05-05 21:45 ` Mike Anderson
2003-05-06 1:12 ` Douglas Gilbert [this message]
2003-05-06 16:28 ` James Bottomley
2003-05-06 17:23 ` Mike Anderson
2003-05-07 23:19 ` Willem Riede
2003-05-08 0:09 ` Douglas Gilbert
2003-05-08 1:44 ` Mike Anderson
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=3EB70BFB.8080009@torque.net \
--to=dougg@torque.net \
--cc=andmike@us.ibm.com \
--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.