From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] blockdev-backup: enable non-root nodes for backup
Date: Mon, 4 Dec 2017 17:15:45 -0500 [thread overview]
Message-ID: <a254716c-2762-3a1c-d4c4-d3abb23f7207@redhat.com> (raw)
In-Reply-To: <8ade3dfe-ec27-a096-5d09-9e694f03935a@redhat.com>
On 12/01/2017 02:41 PM, Max Reitz wrote:
> ((By the way, I don't suppose that's how it should work... But I don't
> suppose that we want propagation of dirtying towards the BDS roots, do
> we? :-/))
I have never really satisfactorily explained to myself what bitmaps on
intermediate notes truly represent or mean.
The simple case is "This layer itself serviced a write request."
If that information is not necessarily meaningful, I'm not sure that's a
problem except in configuration.
...Now, if you wanted to talk about bitmaps that associate with a
Backend instead of a Node...
next prev parent reply other threads:[~2017-12-04 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:16 [Qemu-devel] [PATCH] blockdev-backup: enable non-root nodes for backup Vladimir Sementsov-Ogievskiy
2017-11-09 16:33 ` Eric Blake
2017-11-09 17:29 ` Kevin Wolf
2017-11-09 21:29 ` [Qemu-devel] [Qemu-block] " John Snow
2017-12-01 19:41 ` [Qemu-devel] " Max Reitz
2017-12-04 22:15 ` John Snow [this message]
2017-12-04 22:21 ` [Qemu-devel] [Qemu-block] " Max Reitz
2017-12-05 0:48 ` John Snow
2017-12-08 14:30 ` Max Reitz
2017-12-08 17:09 ` John Snow
2017-12-11 16:31 ` Max Reitz
2017-12-11 16:47 ` John Snow
2017-12-11 17:05 ` Max Reitz
2017-12-11 17:18 ` John Snow
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=a254716c-2762-3a1c-d4c4-d3abb23f7207@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@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).