Hello Eric, I have a question about the behavior of the Linux MPT Fusion SAS driver, and I hope you can clue me in. The microcode of these cards tracks physical devices and once seen makes sure the device shows up with the same physical target number even if you hotplug the SAS disk into a different slot or similar. But it seems that the Linux driver is totally ignoring the topology target numbering provided by the SAS topology scan and simply assigning consequetive indexes, starting at 0, for the target numbers presented to the Linux SCSI layer. It puts a virtual target shim in between these two things so that the mptsas driver can convert the "virtual target" IDs presented to the Linux SCSI layer into the ones indicated by the SAS topology information. Why does it do this? This breaks a lot of things for me on Sparc, for example. There, the device target numbers used by the firmware use the SAS toplogy provided target numbering, whereas the Linux driver uses this (seemingly arbitrary) linear assignment. -- 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
