Artem Bokhan wrote:
It uses ncq. Thanks, Mark.
.. Okay, so the ATA specs explicitly require a reset there. Not much to do about that. If you were super-keen, though, you could crawl through libata and try reducing various delays and polling intervals that are associated with a hard reset for that specific (ahci?) driver and the core libata routines. Might shave that 0.75sec down to perhaps 100ms or so. But again, the optimal numbers in your specific case will not work for the general case. It might be possible to parameterize it all, though, permitting different values for differing hardware. Cheers -- 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
