From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Wolfgang Richter <wolf@cs.cmu.edu>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Wolfgang Richter <wor6c@virginia.edu>
Subject: Re: [Qemu-devel] Adding Disk-Level Introspection to QEMU
Date: Wed, 24 Apr 2013 11:24:40 +0200 [thread overview]
Message-ID: <5177A4D8.3050108@redhat.com> (raw)
In-Reply-To: <20130424083758.GB20971@stefanha-thinkpad.redhat.com>
Il 24/04/2013 10:37, Stefan Hajnoczi ha scritto:
>> > Has there been any performance analysis of drive-mirror (impact on executing guest)?
What Stefan wrote is about block-backup.
drive-mirror has a limited impact on guest performance, but it doesn't
pass the writes through to the channel. Instead, it uses a dirty bitmap
that it periodically scans to copy new data to the destination.
> It slows down guest I/O for a couple of reasons:
>
> 1. Writes now require a read from the original device followed by a
> write to the target device. Only after this completes is the write
> allowed to proceed.
>
> 2. Overlapping read/write requests are serialized to maintain
> consistency between the guests I/Os and the block-backup I/Os.
>
> But on second thought, I don't think block-backup fits the bill. You
> don't care about the original data, you care about what new data the
> guest is writing.
Right. However, when block-backup gets in, I will try to change
drive-mirror to use an "active" method. I don't have a timeframe for
this, though.
Paolo
next prev parent reply other threads:[~2013-04-24 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 17:12 [Qemu-devel] Adding Disk-Level Introspection to QEMU Wolfgang Richter
2013-04-23 17:22 ` Eric Blake
2013-04-23 17:40 ` Wolfgang Richter
2013-04-24 8:37 ` Stefan Hajnoczi
2013-04-24 9:24 ` Paolo Bonzini [this message]
2013-04-24 16:14 ` Wolfgang Richter
2013-04-24 15:59 ` Wolfgang Richter
2013-04-24 19:20 ` Wolfgang Richter
2013-04-23 18:19 ` Stefan Hajnoczi
2013-04-23 18:21 ` Stefan Hajnoczi
2013-04-23 18:31 ` Wolfgang Richter
2013-04-23 19:11 ` Wolfgang Richter
2013-04-24 8:39 ` Stefan Hajnoczi
2013-04-24 16:05 ` Wolfgang Richter
2013-04-24 9:26 ` Paolo Bonzini
2013-04-24 16:14 ` Wolfgang Richter
[not found] ` <CACO=3k4eoT9KwPBgM2eN089=PzzOyBECWgD6MOHz=bzy5EcxAQ@mail.gmail.com>
[not found] ` <51780539.1010303@redhat.com>
2013-04-24 16:43 ` Wolfgang Richter
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=5177A4D8.3050108@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wolf@cs.cmu.edu \
--cc=wor6c@virginia.edu \
/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.