From: Andy Grover <agrover@redhat.com>
To: dgilbert@interlog.com,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
lsf-pc <lsf-pc@lists.linux-foundation.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>
Subject: Re: [LSF/MM ATTEND] iSCSI/iSER MQ + EXTENDED_COPY host support
Date: Thu, 08 Jan 2015 10:58:29 -0800 [thread overview]
Message-ID: <54AED355.5030705@redhat.com> (raw)
In-Reply-To: <54ADAF09.8050405@interlog.com>
On 01/07/2015 02:11 PM, Douglas Gilbert wrote:
> T10 have now dropped the LID1 and LID4 stuff (its the length
> of the LIST IDENTIFIER field: 1 byte or 4 bytes) by obsoleting
> all LID1 variants in SPC-5 revision 01. So the LID1 variants
> are now gone and the LID4 appendage is dropped from the remaining
> commands.
>
> Obviously LID1 based XCOPY support is important for backward
> compatibility (back to SPC-2) but for the future maybe you might
> consider adding the equivalent LID4 support for a basic XCOPY.
> For example it means using the 3PC VPD page instead of the
> RECEIVE COPY RESULTS(operating parameters) command. I believe
> FreeNAS now supports both LID1 and LID4 variants of a basic
> XCOPY (plus a restricted version of ODX without snapshots).
Hi Doug,
I was trying to learn more about ODX and saw this page:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848056%28v=vs.85%29.aspx
but it just muddied the waters for me. Is ODX proprietary to MS, or is
it XCopy lite, or what? And what's the difference between xcopy lite and
LID4 XCOPY?
Thanks -- Andy
next prev parent reply other threads:[~2015-01-08 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 21:21 [LSF/MM ATTEND] iSCSI/iSER MQ + EXTENDED_COPY host support Nicholas A. Bellinger
2015-01-07 22:11 ` Douglas Gilbert
2015-01-08 18:58 ` Andy Grover [this message]
2015-01-08 22:19 ` Nicholas A. Bellinger
2015-01-08 23:11 ` Douglas Gilbert
2015-01-08 23:27 ` Andy Grover
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=54AED355.5030705@redhat.com \
--to=agrover@redhat.com \
--cc=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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).