From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: mreitz@redhat.com, kwolf@redhat.com, den@openvz.org,
pbonzini@redhat.com, armbru@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] NBD export bitmaps
Date: Mon, 30 Apr 2018 16:22:39 -0500 [thread overview]
Message-ID: <6a18337d-1745-aca8-8d64-ccce22d4cefa@redhat.com> (raw)
In-Reply-To: <20180413181401.46318-1-vsementsov@virtuozzo.com>
On 04/13/2018 01:13 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
>
> This is a proposal and realization of new NBD meta context:
> qemu. (I hope to send corresponding proposal to NBD protocol soon)
>
> New possible queries will look like:
> qemu:dirty-bitmap:<export-bitmap-name>
>
>
> qapi/block.json | 23 +++++
> include/block/nbd.h | 6 ++
> blockdev-nbd.c | 23 +++++
> nbd/server.c | 274 ++++++++++++++++++++++++++++++++++++++++++++++------
> 4 files changed, 297 insertions(+), 29 deletions(-)
We need something in docs/interop/ that documents the qemu: namespace
within NBD, so that the upstream NBD spec can point to our document as a
reference for other clients to be aware of what semantics we are exporting.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-04-30 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 18:13 [Qemu-devel] [PATCH v2 0/3] NBD export bitmaps Vladimir Sementsov-Ogievskiy
2018-04-13 18:13 ` [Qemu-devel] [PATCH v2 1/3] nbd/server: add nbd_meta_single_query helper Vladimir Sementsov-Ogievskiy
2018-04-13 18:14 ` [Qemu-devel] [PATCH v2 2/3] nbd/server: implement dirty bitmap export Vladimir Sementsov-Ogievskiy
2018-04-18 14:05 ` Eric Blake
2018-04-19 8:31 ` Vladimir Sementsov-Ogievskiy
2018-04-13 18:14 ` [Qemu-devel] [PATCH v2 3/3] qapi: new qmp command nbd-server-add-bitmap Vladimir Sementsov-Ogievskiy
2018-04-30 21:22 ` Eric Blake [this message]
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=6a18337d-1745-aca8-8d64-ccce22d4cefa@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).