From: Greg KH <greg@kroah.com>
To: Steven Dake <sdake@mvista.com>
Cc: Michael Clark <michael@metaparadigm.com>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] [PATCHES] Advanced TCA Hotswap Support in Linux Kernel
Date: Tue, 15 Oct 2002 13:54:02 -0700 [thread overview]
Message-ID: <20021015205402.GL15864@kroah.com> (raw)
In-Reply-To: <3DAC7EAA.5020408@mvista.com>
On Tue, Oct 15, 2002 at 01:46:34PM -0700, Steven Dake wrote:
> 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.
But what starts the "notification of hotswap"? Is this driven by the
user somehow, or is it a hardware event that happens out of the blue?
> 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.
What generates the hotswap event?
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-15 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 18:42 [ANNOUNCE] [PATCHES] Advanced TCA Hotswap Support in Linux Kernel Steven Dake
2002-10-15 0:59 ` Greg KH
2002-10-15 18:39 ` Steven Dake
2002-10-15 20:42 ` Greg KH
2002-10-15 5:29 ` Greg KH
2002-10-15 17:38 ` Steven Dake
2002-10-15 19:11 ` Michael Clark
2002-10-15 19:28 ` Steven Dake
2002-10-15 20:34 ` Greg KH
2002-10-15 20:46 ` Steven Dake
2002-10-15 20:54 ` Greg KH [this message]
2002-10-15 21:07 ` Steven Dake
2002-10-15 21:16 ` Greg KH
2002-10-15 21:48 ` Steven Dake
2002-10-16 1:05 ` Michael Clark
2002-10-15 20:52 ` Greg KH
[not found] ` <3DAC89FA.9000505@mvista.com>
2002-10-15 22:04 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021015205402.GL15864@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=sdake@mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox