From: James Bottomley <James.Bottomley@SteelEye.com>
To: dougg@torque.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Bodo Eggert <7eggert@gmx.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RFC: Move SG_GET_SCSI_ID from sg to scsi
Date: Mon, 27 Mar 2006 16:22:12 -0600 [thread overview]
Message-ID: <1143498132.3334.28.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <442861C4.7080304@torque.net>
On Mon, 2006-03-27 at 17:05 -0500, Douglas Gilbert wrote:
> I have been reviewing this thread and had one point
> to add here.
>
> The identity of the initiator port is important, at
> least to a SCSI target that can implement (PERSISTENT)
> RESERVE on behalf of one of its logical units.
> So you may need to keep the equivalent of Scsi_Host:this_id
> somewhere.
Since Scsi_Host:this_id is an integer, it's impossible that a
TransportID (which is what you use to identify the port) would ever fit
into it, since these are defined to be at least 24 bytes long.
> That is another shortcoming of the <hctl> tuple: the
> initiator port isn't there.
Actually, it may not be in HCIL, but it is in the transport classes
(although the only implementor is FC at this time, I think). And that's
where it should be since format and contents of the transport ID are
transport specific.
James
next prev parent reply other threads:[~2006-03-27 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 11:03 Bodo Eggert
2006-03-06 19:32 ` Douglas Gilbert
2006-03-07 14:58 ` Stefan Richter
2006-03-27 22:05 ` Douglas Gilbert
2006-03-27 22:22 ` James Bottomley [this message]
2006-03-07 18:49 ` Bill Davidsen
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=1143498132.3334.28.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=7eggert@gmx.de \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®