From: Douglas Gilbert <dougg@torque.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-scsi@vger.kernel.org, ltuikov@yahoo.com,
Jeff Garzik <jgarzik@pobox.com>,
Mike Anderson <andmike@us.ibm.com>,
Luben Tuikov <luben_tuikov@adaptec.com>,
James Bottomley <James.Bottomley@steeleye.com>,
Christoph Hellwig <hch@infradead.org>,
linux-ide@vger.kernel.org
Subject: Re: Adaptec SAS integration notes
Date: Sun, 16 Oct 2005 11:05:07 +1000 [thread overview]
Message-ID: <4351A743.3040105@torque.net> (raw)
In-Reply-To: <43510FEA.6070109@s5r6.in-berlin.de>
Stefan Richter wrote:
> Luben Tuikov wrote:
>
>> --- Jeff Garzik <jgarzik@pobox.com> wrote:
>>
>>> (HCIL should get marginalized, as all agree)
>
>
> "Marginalized" was not the term that I remember.
>
>>> * Put HCIL mapping into top-level helper code, for sharing between FC
>>> and SAS (hopefully!)
>>
>>
>> One step further: eliminate the ugly legacy SPI-centric HCIL from
>> SCSI Core. Minimise and streamline SCSI Core.
>
>
> I agree. FC, SAS, USB, SBP et al do not need to _share_ some HCIL
> mapping helpers --- they and the core need to get rid of HCIL mapping
> entirely. Why spend energy on optimization of existing HCIL mappings?
>
> usb-storage and sbp2 already implement the leanest possible HCIL mapping
> (1 logical unit to 1 H).
Stefan,
Here is a counter example from a USB multicard reader:
$ lsscsi -v
[0:0:0:0] disk Generic USB SD Reader 1.00 /dev/sda
dir: /sys/bus/scsi/devices/0:0:0:0
[/sys/devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:0]
[0:0:0:1] disk Generic USB CF Reader 1.01 /dev/sdb
dir: /sys/bus/scsi/devices/0:0:0:1
[/sys/devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:1]
[0:0:0:2] disk Generic USB SM Reader 1.02 /dev/sdc
dir: /sys/bus/scsi/devices/0:0:0:2
[/sys/devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:2]
[0:0:0:3] disk Generic USB MS Reader 1.03 /dev/sdd
dir: /sys/bus/scsi/devices/0:0:0:3
[/sys/devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:3]
That is 4 logical units to 1 host. [Since I'm often
critical of USB mass storage device SCSI support, in
this case it is good to see some thought went into the
INQUIRY string namings.]
There is an argument for the SCSI subsystem to keep
at least the "l" part of the maligned <h:c:i:l> tuple
because the "l" part really is SCSI (and should be u8[8]).
SATA-II is beginning to struggle along that path as well
with port multipliers of up to 15 devices. SCSI luns
can easily cope with that.
Doug Gilbert
next prev parent reply other threads:[~2005-10-16 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051012184029.GA10786@havoc.gtf.org>
2005-10-14 18:06 ` Adaptec SAS integration notes Luben Tuikov
2005-10-15 14:19 ` Stefan Richter
2005-10-16 1:05 ` Douglas Gilbert [this message]
2005-10-17 6:35 ` Stefan Richter
2005-10-18 16:44 ` Jeff Garzik
2005-10-18 19:30 ` Luben Tuikov
2005-10-18 20:16 ` Jeff Garzik
2005-10-18 20:55 ` Luben Tuikov
2005-10-18 20:36 ` Stefan Richter
2005-10-18 20:51 ` Jeff Garzik
2005-10-15 14:21 James.Smart
2005-10-15 16:01 ` Stefan Richter
2005-10-18 15:06 ` Luben Tuikov
2005-10-18 16:12 ` Luben Tuikov
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=4351A743.3040105@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--cc=andmike@us.ibm.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=luben_tuikov@adaptec.com \
--cc=stefanr@s5r6.in-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).