From: Mike Christie <mchristi@redhat.com>
To: ceph-devel@vger.kernel.org
Cc: ddiss@suse.de
Subject: [PATCH 0/2] ceph osd: initial VMware VAAI support
Date: Thu, 10 Mar 2016 00:36:55 -0600 [thread overview]
Message-ID: <56E11607.8070200@redhat.com> (raw)
In-Reply-To: <1457591672-17430-1-git-send-email-mchristi@redhat.com>
Sorry. Edited the wrong line in the --compose screen. Due to the lack of
subject I guess it is going into some spam filters. Here is the mail:
On 03/10/2016 12:34 AM, Mike Christie wrote:
> The following patches made over the ceph master branch
> implement OSD side support for VMware VAAI's Atomic Test
> and Set (ATS) and Write Same (Zero) requests.
>
> ATS is used for operations like locking and heartbeats. It
> is implemented by as the SCSI COMPARE_AND_WRITE command which
> requires the device to read N blocks, compare them to data
> sent with the command, and if equal, write N blocks.
>
> Zero is used to initialize blocks to zero. It is implemented
> as the SCSI WRITE_SAME command which passes the device a
> block's worth of data and has it write it multiple times.
>
> This does not include support for XCOPY/extended copy. I
> am still looking into this, but it seems it might be
> difficult to support due to rbd being more tuned to cloning
> entire devices. When we implement VASA, the cloneVirtualVolume
> might be something we can support though.
>
> More info on VAAI can be found here:
> http://www.vmware.com/resources/techresources/10337
>
> The krbd patches which use these requests are in vaai branch of
> this tree:
> https://github.com/mikechristie/linux-kernel
>
> I did not submit them in this thread, because they depend on other
> patches that are still being reviewed upstream and I did not want
> to waste people's time reviewing them if they change. These OSD side
> patches should be ok to review and merge, because the op format
> and implemention should not change.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-03-10 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 0/2] ceph osd: initial VMware VAAI support>
2016-03-10 6:34 ` (unknown), Mike Christie
2016-03-10 6:34 ` [PATCH 1/2] ceph osd: add support for new op writesame Mike Christie
2016-03-10 12:03 ` David Disseldorp
2016-03-10 6:34 ` [PATCH 2/2] ceph osd: add support for new op cmpext Mike Christie
2016-03-10 12:03 ` David Disseldorp
2016-03-10 17:06 ` Mike Christie
2016-03-10 17:12 ` David Disseldorp
2016-03-10 6:36 ` Mike Christie [this message]
2016-03-10 12:04 ` [PATCH 0/2] ceph osd: initial VMware VAAI support David Disseldorp
2016-03-10 22:45 ` Josh Durgin
2016-03-11 4:46 ` Ric Wheeler
2016-03-11 10:03 ` David Disseldorp
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=56E11607.8070200@redhat.com \
--to=mchristi@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ddiss@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.