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 14:07:43 -0700	[thread overview]
Message-ID: <3DAC839F.7060301@mvista.com> (raw)
In-Reply-To: 20021015205402.GL15864@kroah.com



Greg KH wrote:

>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?
>  
>
In the case of Advanced TCA, an IPMI message is sent to the CPU blade 
indicating the hotswap button is pressed on the front panel of a disk 
blade.  The hotswap manager software unmaps the GA address, removes the 
device from the linux kernel via the scsi-hotswap-main stuff, and sends 
another IPMI message to the disk node telling it to light its "blue 
led".  The user removes the disk.  Insertion is easier.

In this case, the hotswap button on the front panel is used to indicate 
a hotswap event.  There is talk of making the removal of the board 
indicate a hotswap event (surprise extraction) because the technicians 
don't wait for the blue led to remove the boards occasionally and the 
system should be able to handle this use case.

>>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?
>  
>
In the case of SAFTE, a SCSI processor (ASIC) is polled by some polling 
interval about the state of the SAFTE (SCSI) backplane.  When the state 
changes, software generates a hotswap event and removes the device.

Thanks
-steve

>  
>


  reply	other threads:[~2002-10-15 21:01 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
2002-10-15 21:07               ` Steven Dake [this message]
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=3DAC839F.7060301@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