Albert Lee wrote:
It's worthwhile to poll alt_status and wait for BSY to clear in this case.
Polling the ATA ALT_STATUS register can take up to 600ns, or the equivalent of several thousand wasted instructions on a modern CPU. It's only worthwhile if the poll was actually necessary. My question is, do we really want this overhead in the hot path on every single ATA interrupt, or should we instead simply blacklist those devices with the problem? Or perhaps be more clever in handling it: If the device driver interrupt routine see's BUSY still set after the normal ATA STATUS read, *then* we could do the poll. That way it never adds unnecessary overhead. This is more than "just a single instruction" here.. it's the equivalent of thousands of them, each time we read an ATA register. 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
