From: Douglas Gilbert <dougg@torque.net>
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
Subject: Re: [PATCH] /proc/scsi/map
Date: Sat, 22 Jun 2002 16:11:29 -0400 [thread overview]
Message-ID: <3D14D9F1.8B88668F@torque.net> (raw)
In-Reply-To: Pine.LNX.4.44.0206221943320.8911-100000@serv
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
next prev parent reply other threads:[~2002-06-22 20:12 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 17:24 [PATCH] /proc/scsi/map David Brownell
2002-06-22 17:48 ` Roman Zippel
2002-06-22 20:11 ` Douglas Gilbert [this message]
2002-06-22 20:57 ` Roman Zippel
2002-06-22 18:18 ` Nick Bellinger
2002-06-24 1:50 ` David Brownell
2002-06-25 16:46 ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 17:47 ` driverfs bus_id, name (was: [PATCH] /proc/scsi/map) David Brownell
2002-06-25 19:06 ` Patrick Mochel
2002-06-25 19:55 ` David Brownell
2002-07-01 17:25 ` Patrick Mochel
2002-06-25 17:49 ` [PATCH] /proc/scsi/map David Brownell
2002-06-26 23:39 ` Nick Bellinger
2002-07-01 17:45 ` Patrick Mochel
2002-07-03 0:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-06-22 6:29 Adam J. Richter
2002-06-25 16:17 ` Patrick Mochel
2002-06-20 23:59 Grover, Andrew
2002-06-20 0:44 Kurt Garloff
2002-06-20 5:03 ` Linus Torvalds
2002-06-20 7:09 ` Martin Schwenke
2002-06-20 15:13 ` Linus Torvalds
2002-06-20 15:36 ` Dave Jones
2002-06-20 17:01 ` Linus Torvalds
2002-06-20 16:55 ` Andries Brouwer
2002-06-20 17:52 ` Patrick Mansfield
2002-06-20 18:36 ` Linus Torvalds
2002-06-20 18:52 ` James Bottomley
2002-06-20 19:15 ` Linus Torvalds
2002-06-20 16:28 ` Benjamin Herrenschmidt
2002-06-21 0:46 ` Linus Torvalds
2002-06-20 16:49 ` Benjamin Herrenschmidt
2002-06-20 20:06 ` Oliver Xymoron
2002-06-22 18:27 ` Pavel Machek
2002-06-20 18:11 ` Linus Torvalds
2002-06-20 22:59 ` Martin Schwenke
2002-06-20 23:13 ` Linus Torvalds
2002-06-22 18:25 ` Pavel Machek
2002-06-26 16:03 ` Ihno Krumreich
2002-07-01 17:33 ` Patrick Mochel
2002-06-20 19:55 ` Greg KH
2002-06-20 19:18 ` Patrick Mochel
2002-06-21 6:28 ` Mike Touloumtzis
2002-06-20 11:25 ` Kurt Garloff
2002-06-20 15:34 ` Linus Torvalds
2002-06-20 16:30 ` Martin Dalecki
2002-06-20 16:58 ` James Bottomley
2002-06-20 18:27 ` Linus Torvalds
2002-06-20 20:55 ` Martin Dalecki
2002-06-20 21:04 ` Linus Torvalds
2002-06-20 21:36 ` Martin Dalecki
2002-06-20 20:12 ` Patrick Mochel
2002-06-20 22:29 ` Martin Dalecki
2002-06-22 18:42 ` Pavel Machek
2002-06-21 14:29 ` sullivan
2002-06-21 16:17 ` Patrick Mochel
2002-06-21 21:33 ` Oliver Xymoron
2002-06-22 4:38 ` Nick Bellinger
2002-06-22 19:41 ` Douglas Gilbert
2002-06-22 19:11 ` Nick Bellinger
2002-06-25 18:13 ` Patrick Mochel
2002-06-25 16:05 ` Patrick Mochel
2002-06-25 16:57 ` Oliver Xymoron
2002-06-25 18:58 ` Patrick Mochel
2002-07-03 1:01 ` Pavel Machek
2002-06-20 18:32 ` Kurt Garloff
2002-06-20 18:53 ` Linus Torvalds
2002-06-21 9:07 ` Kurt Garloff
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=3D14D9F1.8B88668F@torque.net \
--to=dougg@torque.net \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nickb@attheoffice.org \
--cc=zippel@linux-m68k.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