> But more importantly, it takes roughly half a second to set up the > device. I understand, that the probing is part of AHCI(?), and in this > case the Crucial m4 SSD drive/firmware is especially slow. So, I assume > it will be hard to improve anything in the code to decrease the time. Probably. The OS basically waits for the device to flag read. It's not that slow (spinning rust can take several seconds, and historically up to 30) > So, is there a way to avoid doing the probing twice or at all? That You have to do it once. It's not probing that is slow. Your SSD is basically a single board computer pretending to be a disk. It's go to boot and load in and work out what the hell it's doing, what happened before it died and so on. Spinning rust is similar - in fact with a modern ATA disk plugged into a really old machine it's not uncommon that the disk has the most CPU power 8) Once you have completed the boot for that channel (so for SATA pretty much for that device) you could in theory pass the OS a flag saying 'is initialized, is present' and you'd be able to avoid a repeat reset/probe and just go on to re-issue identify and similar commands in order to re-obtain the configuration data of the drive. Those commands are fast on any hardware I've seen. This is known to work for straigt ATA - it's sort of what we do in the corner cases where we find an ATA class controller we don't support. AHCI is a bit more complex but the theory should hold. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
