From: "Prasenjit Sarkar" <psarkar@almaden.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: SCSI Patches - mostly on/off-line stuff
Date: Thu, 18 Jan 2001 16:49:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97983653306720@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97925037703688@msgid-missing>
[I was told that FCP did not support AENs but I might be mistaken.]
In general, as SCSI becomes more networked, most approaches will want the
initiator to figure out what is the
current list of targets the initiator is connected to, rather than the
targets trying to inform interested initiators whether
the targets are coming on-line or going off-line.
Keeping that in mind, a bus rescan is a better way to go (where a bus is
'virtual' for networked SCSI architectures).
-prasenjit
Prasenjit Sarkar
Research Staff Member
IBM Almaden Research
San Jose
Venkatesh Ramamurthy <Venkateshr@ami.com>@vger.kernel.org on 01/18/2001
08:20:03 AM
Sent by: linux-scsi-owner@vger.kernel.org
To: "'Eric Youngdale'" <eric@andante.org>, Douglas Gilbert
<dougg@torque.net>, David Brownell <david-b@pacbell.net>
cc: linux-scsi@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: RE: SCSI Patches - mostly on/off-line stuff
> Anyways, my initial question reallly has to do with exactly how one
is
> notified that a new device has appeared and whether a bus scan needs to
be
> initiated or not. That will control the degree to which we have to
screw
> with things in the mid-layer to support this.
>
[Venkat] Some of the SCSI devices support AEN, which the low level
driver can use to detect any addition in BUS. I not sure whether all the
scsi device do support it. If this the scsi case low level driver can call
the SCSI ML to add the new device. I dont whether this is a general
solution.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-18 16:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 21:56 SCSI Patches - mostly on/off-line stuff Douglas Gilbert
2001-01-11 22:43 ` Oliver.Neukum
2001-01-17 20:32 ` David Brownell
2001-01-18 0:08 ` Douglas Gilbert
2001-01-18 9:03 ` Oliver Neukum
2001-01-18 9:25 ` Miles Lane
2001-01-18 15:37 ` Eric Youngdale
2001-01-18 16:20 ` Venkatesh Ramamurthy
2001-01-18 16:49 ` Prasenjit Sarkar [this message]
2001-01-18 16:50 ` Venkatesh Ramamurthy
2001-01-18 17:03 ` Venkatesh Ramamurthy
2001-01-18 18:14 ` David Brownell
2001-01-18 19:12 ` Oliver Neukum
2001-01-18 19:20 ` Prasenjit Sarkar
2001-01-18 19:45 ` Miles Lane
2001-01-18 21:08 ` Douglas Gilbert
2001-01-18 21:41 ` Miles Lane
2001-01-18 22:07 ` David Brownell
2001-01-18 22:15 ` David Brownell
2001-01-18 22:45 ` Oliver Neukum
2001-01-18 23:10 ` Oliver Neukum
2001-01-18 23:25 ` Miles Lane
2001-01-18 23:37 ` Oliver Neukum
2001-01-19 2:08 ` David Brownell
2001-01-19 2:10 ` Bob Frey
2001-01-19 2:16 ` Venkatesh Ramamurthy
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=marc-linux-hotplug-97983653306720@msgid-missing \
--to=psarkar@almaden.ibm.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).