From: Eric Blake <eblake@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 8/8] qemu-iotests: test streaming to an intermediate layer
Date: Wed, 22 Apr 2015 13:54:33 -0600 [thread overview]
Message-ID: <5537FC79.5090809@redhat.com> (raw)
In-Reply-To: <dad8718832c048dbccdef4c6676ba2d97ae616fe.1429196435.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On 04/16/2015 09:12 AM, Alberto Garcia wrote:
> This adds test_stream_intermediate(), similar to test_stream() but
> streams to the intermediate image instead.
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
> tests/qemu-iotests/030 | 18 +++++++++++++++++-
> tests/qemu-iotests/030.out | 4 ++--
> 2 files changed, 19 insertions(+), 3 deletions(-)
>
I'm wondering if we should also test a multi-file stream. That is,
starting from:
A <- B <- C <- D <- E
and rebasing so that A is the backing file of D (pulling both B and C
into D):
A <- D <- E
we should be able to verify that B and C are unchanged, and that D
picked up changes from both intermediate files (in particular, it's nice
to test that we aren't being inefficient by breaking the operation into
two steps: streaming B into C then C into D would give the same end
result in D, but would waste time for any clusters in B that were not
changed in C but were changed in D).
But such a test could be a separate patch, so I don't see anything wrong
with this new test as-is.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-04-22 19:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 15:12 [Qemu-devel] [PATCH v4 0/8] Support streaming to an intermediate layer Alberto Garcia
2015-04-16 15:12 ` [Qemu-devel] [PATCH 1/8] block: keep a list of block jobs Alberto Garcia
2015-04-22 20:00 ` Eric Blake
2015-04-16 15:12 ` [Qemu-devel] [PATCH 2/8] block: allow block jobs in any arbitrary node Alberto Garcia
2015-04-22 17:15 ` Max Reitz
2015-04-22 20:06 ` Eric Blake
2015-04-23 9:04 ` Alberto Garcia
2015-04-16 15:12 ` [Qemu-devel] [PATCH 3/8] block: never cancel a streaming job without running stream_complete() Alberto Garcia
2015-04-16 15:12 ` [Qemu-devel] [PATCH 4/8] block: Support streaming to an intermediate layer Alberto Garcia
2015-04-22 17:23 ` Max Reitz
2015-04-16 15:12 ` [Qemu-devel] [PATCH 5/8] block: Add QMP support for " Alberto Garcia
2015-04-22 17:26 ` Max Reitz
2015-04-22 20:10 ` Eric Blake
2015-04-16 15:12 ` [Qemu-devel] [PATCH 6/8] docs: Document how to stream " Alberto Garcia
2015-04-22 17:29 ` Max Reitz
2015-04-22 19:27 ` Eric Blake
2015-04-16 15:12 ` [Qemu-devel] [PATCH 7/8] qemu-iotests: fix test_stream_partial() Alberto Garcia
2015-04-22 17:54 ` Max Reitz
2015-04-22 19:38 ` Eric Blake
2015-04-22 19:52 ` Alberto Garcia
2015-04-16 15:12 ` [Qemu-devel] [PATCH 8/8] qemu-iotests: test streaming to an intermediate layer Alberto Garcia
2015-04-22 17:56 ` Max Reitz
2015-04-22 19:54 ` 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=5537FC79.5090809@redhat.com \
--to=eblake@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).