linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Steven Dake <sdake@mvista.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [RFC] Advanced TCA SCSI Disk Hotswap
Date: Thu, 24 Oct 2002 09:25:12 -0500	[thread overview]
Message-ID: <200210241425.g9OEPCP02249@localhost.localdomain> (raw)
In-Reply-To: Message from Steven Dake <sdake@mvista.com> of "Wed, 23 Oct 2002 17:48:46 PDT." <3DB7436E.9060100@mvista.com>

I looked at this briefly last night.  The patch seems to come in three pieces:

1) Add list locking to manipulations of the host device list
2) Add a new filesystem type for exposing SCSI information
3) add a lot more methods for adding and removing SCSI devices.

1) seems to be something we should have

I'm dubious about 2).  Could you explain why you need a new fs interface as 
opposed to using driverfs?

3) duplicates existing functionality and the new bits it does add could be 
done using a hotplug framework.

For all the removes, if you exposed the information you're looking for (FC 
wwn) in driverfs, you could use the existing remove interface.

For the adds, all of this would be finessed by having the FC event that 
detected a new device on the fibre trigger a hotplug event.  You could then 
have the hotplug trigger the existing add device interface to make the 
component configure automatically (hotplug on fibre events like this has been 
a hot item for a while, so having a general interface would be most welcome).

If you must delay configuration and do it by wwn later, you could capture the 
wwns to host,channel,id,lun mappings in a table on the hotplug event (and not 
configure the device) and use the information for later configuration using 
the existing interfaces.

James



  reply	other threads:[~2002-10-24 14:25 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 [this message]
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
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=200210241425.g9OEPCP02249@localhost.localdomain \
    --to=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).