--- Christoph Hellwig <hch@xxxxxx> wrote:
> > For SAS, looking at Christoph's code -
> > The target id comes from the LLDD.
>
> This is just a brindup helper because the Fusion hardware does a SAS
> remote port to target ID mapping in firmware, in fact the firmware
> interface only addresses them using this assigned ID, which is a big
> shortcoming in the Fusion interface. Once the more basic things are
:-)
> dealt with that will go away, similarly to how Fusion won't be able
> to use their firmware mapping for FC once they fully support the FC
> transport class.
You should not deny the possibility of vendors providing "HCIL" or
any other (kind of) label for the LU.
However it is possible to move into the 21st century _and_ provide
HCIL or any other (kind of) label to anyone who's interested.
Vendors would want to name the LU something, so that it is identifiable
to end users. Vendors may want to provide one or many labels.
Luben
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
