The data/telecoms I've talked to require disk hotswap times of less then
20 msec from notification of hotwap to blue led (a light used to
indicate the device can be removed). They would like 10 msec if it
could be done. This is because of how long it takes on a surprise
extraction for the hardware to send the signal vs the user to disconnect
the hardware.
For legacy systems such as SAFTE hotswap, polling through sg at 10 msec
intervals would be extremely painful because of all the context
switches. A timer scheduled every 10 msec to send out a SCSI message
and handle a response if there is a hotswap event is a much better course.
Thanks
-steve
Greg KH wrote:
>On Tue, Oct 15, 2002 at 12:28:59PM -0700, Steven Dake wrote:
>
>
>>Safte polling in the kernel isn't inherently bad and could be tied into
>>the hotplug mechanism.
>>
>>Making SAFTE hotswap available via SG would also work but system
>>performance would be bad at small poll intervals (like 100 msec).
>>
>>
>
>Is there a real nead to get hotplug notification any faster than that?
>
>And yes, it should all be done in userspace, whenever possible :)
>
>thanks,
>
>greg k-h
>
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:57 EST