Alan Cox wrote: >> async probing also keeps device numbering stable. As long as the device >> responds within ten seconds (and the current code has half a second as >> the timeout), it'll get the same number it would have had, even though >> other hosts have successfully completed their probes during that time. > > The usual probe time for a device which is spun down is nearer 30 seconds. libata probing is done differently tho. It goes like... 1. libata EH probes all hardware. Things can take quite long here but SCSI isn't really involved. 2. After libata EH is finished, SCSI host scan is invoked. It doesn't do much. When SCSI probing command reaches libata-scsi, it just fakes the replies from the information gathered in #1 - No actual ATA reset or command is issued. If there are multiple devices on a host (ATA port), this rapid probing makes SCSI host scan code fail GFP_ATOMIC allocation from time to time. This is why the @sync hack was used. Thanks. -- tejun - 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
