On Sat, 2009-05-02 at 15:51 -0700, David Miller wrote: > From: "Moore, Eric" <Eric.Moore@xxxxxxx> > Date: Sat, 2 May 2009 16:44:54 -0600 > > > the sas transport layer is assigning the target id's > > Can you show me where that happens and how the MPT fusion > SAS driver exports the SAS topology target IDs to that > layer? It happens in scsi_transport_sas.c:sas_rphy_add() which uses the sas_host_attr's next_target_id to track a monotonically increasing number for the SCSI target id (it gets incremented every time a remote port is added to the system). What the SAS spec defines as the target id is really a 64 bit WWPN, which was difficult at the time to place in the SCSI mid layer SPI based concept of a target. If the fusion is also defining some number as a target id that isn't the WWPN, then we could export that as well somewhere ... that's essentially what we did for the qlogic and emulex persistent bindings. James -- To unsubscribe from this list: 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
