linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Steven Dake <sdake@mvista.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [RFC] Advanced TCA SCSI Disk Hotswap
Date: Thu, 24 Oct 2002 15:58:49 -0700	[thread overview]
Message-ID: <20021024225849.GG1563@beaverton.ibm.com> (raw)
In-Reply-To: <200210242002.g9OK27W03864@localhost.localdomain>

James Bottomley [James.Bottomley@steeleye.com] wrote:
> sdake@mvista.com said:
> > I plan to produce a now patch that dumps the filesystem interface and
> > replaces it with driverfs files in /sys/bus/scsi.  These things take
> > time, but I hope to be  finished by October 25th. 
> 
> OK, that's good, thanks.
> 

A note here is that the SCSI device model still may need to be altered. I
am having issues of trying to fill out support and in looks like we
might have to restructure a few things. 

If the nodes are structure under your own directory they should be ok.

It makes a asymmetric interface, but some parameters can be applied on
removal by a cd to the correct leaf node.

Lock operations are somewhat simplified if we convert some of these
operations to the device model.

> There will be a point where for a large number of drivers, a linear scan even 
> in the kernel will be slower than a good DB lookup in userspace.
> 
> > Hotplugs on FibreChannel don't trigger "events".  What they can do is
> > LIP (loop initialization procedure) if the device has been configured
> > in it's SCSI code pages to  do such a thing.  Since this is device
> > specific I'd hate to rely on it for hotswap. 
> 
> They don't now, but they should.  The LIP protocol makes the FC driver aware 
> of the gain or loss of devices.  This should be communicated to the mid-layer 
> and then trigger a hotplug event.  Someone needs to write this, I was just 
> wondering if you might.

In switched FC fabrics you do receive SCNs if you have registered for
them which most adapters do. 

We already have interface support from the device model we just need to make the
calls.

-andmike
--
Michael Anderson
andmike@us.ibm.com


  parent reply	other threads:[~2002-10-24 22:58 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
2002-10-27 15:08             ` Rob Landley
2002-10-27 20:25               ` Randy.Dunlap
2002-10-24 22:58       ` Mike Anderson [this message]
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=20021024225849.GG1563@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --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).