From mboxrd@z Thu Jan  1 00:00:00 1970
From: Douglas Gilbert <dougg@torque.net>
Subject: Re: [PATCH] /proc/scsi/map
Date: Sat, 22 Jun 2002 16:11:29 -0400
Sender: linux-scsi-owner@vger.kernel.org
Message-ID: <3D14D9F1.8B88668F@torque.net>
References: <Pine.LNX.4.44.0206221943320.8911-100000@serv>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-path: <linux-scsi-owner@vger.kernel.org>
List-Id: linux-scsi@vger.kernel.org
To: Roman Zippel <zippel@linux-m68k.org>
Cc: David Brownell <david-b@pacbell.net>, Nick Bellinger <nickb@attheoffice.org>, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org

Roman Zippel wrote:
> 
> Hi,
> 
> On Sat, 22 Jun 2002, David Brownell wrote:
> 
> > Why shouldn't there be a $DRIVERFS/net/ipv4@10.42.135.99/... style hookup
> > for iSCSI devices?  Using whatever physical addressing the kernel uses
> > there, which I assume wouldn't necessarily be restricted to ipv4.
> 
> iSCSI devices are uniqely identified by its name. An iSCSI device can be
> reachable at multiple ip numbers or they can even change dynamically.

Roman,
Trying to clear up the nomenclature here, according to SAM-2
( www.10.org ) target ports have mandatory "identifiers"
and optional "names". The WWUI in iSCSI is part of the
target _identifier_. SAM-2 is pretty vague about "names"
but it does note that for a logical unit, its _name_
may be reported in the Device Identification VPD page in
an INQUIRY. 


Doug Gilbert