public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: James.Smart@Emulex.Com
Cc: matthew@wil.cx, forrest.zhao@intel.com,
	linux-scsi@vger.kernel.org, ramesh.caushik@intel.com
Subject: Re: One question about SCSI device hotplug
Date: Tue, 1 Mar 2005 22:42:38 -0600	[thread overview]
Message-ID: <20050302044238.GA20042@lists.us.dell.com> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12EC5E@xbl3.ma.emulex.com>

On Tue, Mar 01, 2005 at 11:35:28AM -0500, James.Smart@Emulex.Com wrote:
> > On Tue, Mar 01, 2005 at 05:06:55PM +0800, Zhao, Forrest wrote:
> > > If I surprisingly hot-remove a SCSI disk from HBA manually 
> > > without executing "echo "scsi remove-single-device
> > >  <h> <b> <t <l>" > /proc/scsi/scsi", can the "hotplug"
> > > event be notified to SCSI mid-layer or user space?
> > > 
> > > I briefly browse some code of LLDD, it seems that LLDD never
> > > report "hotplug" event to upper-level layer. Am I right?
> > 
> > I don't think it *can* ... the SCSI protocols don't tell the 
> > host "hey,
> > this device has disappeared".
> 
> All depends on what transport it is... In FC, we can detect when
> a target is removed. In the most recent FC transport code (not
> all integrated yet), it will indeed automagically invoke
> scsi_remove_device() for all luns on the target.

And in the patches I posted a couple weeks ago, userspace can notify
the kernel about an added/removed device if it knows about it but the
kernel doesn't (say, a management app does the add/remove but the LLDD
doesn't get an interrupt from the firmware on such events).

There's also the slave_{alloc,configure,destroy} callbacks in the
drivers, that let the LLDDs know about a LUN creation or removal, if
you've got device state stored in the driver.

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2005-03-02  4:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 16:35 One question about SCSI device hotplug James.Smart
2005-03-02  4:42 ` Matt Domsch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02 15:51 James.Smart
2005-03-02  5:33 Zhao, Forrest
2005-03-02  4:47 Zhao, Forrest
2005-03-02  4:57 ` Matt Domsch
2005-03-02  3:40 Rajat  Jain, Noida
2005-03-01 15:20 Nagpure, Dinesh
2005-03-01  9:06 Zhao, Forrest
2005-03-01 14:46 ` Matthew Wilcox

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=20050302044238.GA20042@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=James.Smart@Emulex.Com \
    --cc=forrest.zhao@intel.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=ramesh.caushik@intel.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