From: Patrick Mansfield <patmans@us.ibm.com>
To: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
Cc: Douglas Gilbert <dougg@torque.net>, linux-scsi@vger.kernel.org
Subject: Re: [RFC] SCSI Hotplug for lk 2.5
Date: Fri, 2 Aug 2002 12:58:40 -0700 [thread overview]
Message-ID: <20020802125840.A795@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <200208021113.g72BD2m01761@fachschaft.cup.uni-muenchen.de>; from Oliver.Neukum@lrz.uni-muenchen.de on Fri, Aug 02, 2002 at 11:40:29AM +0200
On Fri, Aug 02, 2002 at 11:40:29AM +0200, Oliver Neukum wrote:
>
> How about new paths to a device? It seems that the FibreChannel
> people need that.
It is not only fibrechannel - dual initiated busses, dual ported
devices, maybe iSCSI and maybe other low level drivers can have
mutiple paths to the actual device.
Did you see Doug's:
e) for multipath devices I would expect a hotplug alert for
each path a device is discovered on (perhaps this is not
practical)
With my current multi-path code, a hotplug per path is possible, and
not difficult to add. The device alert (as Doug describes) already includes
a path, we probably would also need some flag that says this is the first
path; on removal, you would want a flag saying if this was the last path.
User level code would have to notice (for example) that a device was
already found and mounted, and that this is just another path to the device.
-- Patrick Mansfield
next prev parent reply other threads:[~2002-08-02 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 22:57 [RFC] SCSI Hotplug for lk 2.5 Douglas Gilbert
2002-08-02 9:40 ` Oliver Neukum
2002-08-02 19:58 ` Patrick Mansfield [this message]
2002-08-02 20:37 ` Matthew Dharm
2002-08-02 21:21 ` Matthew Jacob
2002-08-03 1:27 ` Patrick Mansfield
[not found] <17amcn-1uCpTkC@fmrl06.sul.t-online.com>
2002-08-03 0:20 ` Matthew Jacob
-- strict thread matches above, loose matches on Subject: below --
2002-08-05 15:09 Cress, Andrew R
2002-08-06 22:43 ` Patrick Mansfield
2002-08-07 4:21 ` Matthew Jacob
2002-08-07 15:56 Cress, Andrew R
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=20020802125840.A795@eng2.beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
/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