[7687] in linux-scsi channel archive
Re: How do I invoke a re-probe/Hot Plugging Devices
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Mon Dec 13 13:06:56 1999
Message-ID: <00a201bf4593$ebe75a60$940310ac@fairfax.datafocus.com>
From: "Eric Youngdale" <eric@andante.org>
To: "Robert Frey" <bobf@advansys.com>
Cc: <linux-scsi@vger.rutgers.edu>
Date: Mon, 13 Dec 1999 13:00:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Oh, I agree that it is interesting. It is just that I really don't want
to do more than flap my gums until the queueing code has settled in for a
bit, however. There are some interesting architectural issues that require
some thought before any code gets written....
-Eric
----- Original Message -----
From: Robert Frey <bobf@advansys.com>
To: <alan@lxorguk.ukuu.org.uk>; <eric@andante.org>
Cc: <linux-scsi@vger.rutgers.edu>
Sent: Monday, December 13, 1999 12:36 PM
Subject: Re: How do I invoke a re-probe/Hot Plugging Devices
> Eric wrote:
> > If you can ensure that the host is otherwise idle, then I would
> > feel more comforatable about adding and removing new devices on the fly.
> >
> Interesting topic! Hot plugging of (SCSI) devices is something that needs
> to be architecturally handled in the future. 1394 (SBP2) and FibreChannel
> (FCP-SCSI) both support SCSI command set devices that are hot pluggable
> without notification to the OS (surprise removal). Is anybody working on
> these issues? Ideally I don't think hot plugging can be handled in bus
> specific ways - it should be handled by the whole I/O system must identify
> a device by its global unique id and bus reset generation count.
>
> Bob Frey
> bobf@advansys.com
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
