From: "Ewan D. Milne" <emilne@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
dm-devel@vger.kernel.org
Subject: [LSF/MM TOPIC] [LSF/MM ATTEND] XCOPY
Date: Fri, 09 Dec 2016 09:22:12 -0500 [thread overview]
Message-ID: <1481293332.28416.282.camel@localhost.localdomain> (raw)
I'd like to attend LSF/MM this year, and I'd like to discuss
XCOPY and what we need to do to get this functionality
incorporated. Martin/Mikulas' patches have been around for
a while, I think the last holdup was some request flag changes
that have since been resolved.
We do need to have a token-based XCOPY implementation as that
is what the array vendors are supporting.
-Ewan
reply other threads:[~2016-12-09 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1481293332.28416.282.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=dm-devel@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).