public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: Greg KH <greg@kroah.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:46:34 -0700	[thread overview]
Message-ID: <3DAC7EAA.5020408@mvista.com> (raw)
In-Reply-To: 20021015203423.GI15864@kroah.com

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
>
>
>
>  
>


  reply	other threads:[~2002-10-15 20:38 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 [this message]
2002-10-15 20:54             ` Greg KH
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=3DAC7EAA.5020408@mvista.com \
    --to=sdake@mvista.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.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