From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Steven Dake <sdake@mvista.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] Advanced TCA SCSI Disk Hotswap
Date: Thu, 24 Oct 2002 19:52:53 -0400 [thread overview]
Message-ID: <3DB887D5.5080500@pobox.com> (raw)
In-Reply-To: 200210242342.g9ONgGT04819@localhost.localdomain
James Bottomley wrote:
>>n Advanced TCA (what spawned this work) a button is pressed to
>>indicate hotswap removal which makes for easy detection of hotswap
>>events. This is why there are kernel interfaces for removal and
>>insertion (so a kernel driver can be written to detect the button
>>press and remove the devices from the os data structures and then
>>light a blue led indicating safe for removal).
>>
>>
>
>OK, I understand what's going on now. It's no different from those hotplug
>PCI busses where you press the button and a second or so later the LED goes
>out and you can remove the card. 10ms sounds rather a short maximum time for
>a technician to wait for a light to go out....I suppose Telco technicians are
>rather impatient.
>
>I really think you need to lengthen this interval. The kernel is moving
>towards this type of hotplug infrastructure which you can easily leverage (or
>even help build), but it's definitely going to be mainly in user space.
>
>
Caveat coder -- you also have to handle the case where the device is
already gone, by the time you are notified of the hot-unplug event.
Some ejections are less friendly than others... though from a SCSI
standpoint, hopefully that case is easier -- error out all I/Os in
flight, and unregister the host and device structures associated with
the recently-removed host. The devil, of course, is in the details ;-)
Jeff
next prev parent reply other threads:[~2002-10-24 23:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 0:48 [PATCH] [RFC] Advanced TCA SCSI Disk Hotswap Steven Dake
2002-10-24 14:25 ` James Bottomley
2002-10-24 19:40 ` Steven Dake
2002-10-24 20:02 ` James Bottomley
2002-10-24 20:45 ` Steven Dake
2002-10-24 21:05 ` Randy.Dunlap
2002-10-24 21:48 ` Steven Dake
2002-10-24 23:00 ` Scott Murray
2002-10-24 23:22 ` Greg KH
2002-10-24 23:48 ` Steven Dake
2002-10-25 0:20 ` Jeff Garzik
2002-10-25 10:04 ` Alan Cox
2002-10-25 0:18 ` Scott Murray
2002-10-24 23:42 ` James Bottomley
2002-10-24 23:52 ` Jeff Garzik [this message]
2002-10-27 15:08 ` Rob Landley
2002-10-27 20:25 ` Randy.Dunlap
2002-10-24 22:58 ` Mike Anderson
2002-10-24 22:32 ` Patrick Mansfield
2002-10-24 22:36 ` Mike Anderson
2002-10-24 22:47 ` Steven Dake
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=3DB887D5.5080500@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).