Christoph Hellwig wrote:
On Wed, Jan 04, 2006 at 02:58:40PM -0700, Moore, Eric wrote:
The sas transport current implementation is mapping
the channel number for each sas/sata device equal to
the phy number. The problem with that is it will be difficult
to reserve a channel for RAID volumes when hot swap support
is eventually implemented in the sas transport layer.
Thus my suggested change is to map the channel to the port
identifier, which effectively maps each channel number to its own
unique sas domain. Thus we can map the RAID volumes to a reserved
channel that
is one larger than the anticapated number of ports on the direct
attached host
adapter.
ACK. The channel isn't used for anything in the transport class or LLDD,
so this is fine.
Is it desired to provide content for "channel" in non-SPI transport
classes, IOW to semantically overload "channel"? (Short term, long term...?)
--
Stefan Richter
-=====-=-==- ---= --===
http://arcgraph.de/sr/
-
: 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
