From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Chris Wright <chrisw@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com, Dor Laor <dlaor@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for June 28
Date: Thu, 30 Jun 2011 14:39:41 +0200 [thread overview]
Message-ID: <4E0C6E8D.9040705@redhat.com> (raw)
In-Reply-To: <BANLkTinkZmGmkte8iDXzU5twZ7sbzY1aMQ@mail.gmail.com>
Am 30.06.2011 13:48, schrieb Stefan Hajnoczi:
> On Wed, Jun 29, 2011 at 4:41 PM, Marcelo Tosatti <mtosatti@redhat.com> wrote:
>> On Wed, Jun 29, 2011 at 11:08:23AM +0100, Stefan Hajnoczi wrote:
>>> In the future we could add a 'base' argument to block_stream. If base
>>> is specified then data contained in the base image will not be copied.
>>
>> This is a present requirement.
>
> It's not one that I have had in the past but it is a reasonable requirement.
>
> One interesting thing about this requirement is that it makes
> copy-on-read seem like the wrong primitive for image streaming. If
> there is a base image which should not be streamed then a plain loop
> that calls bdrv_is_allocated_chain(bs, base, sector, &pnum) and copies
> sectors into bs is more straightforward than passing base to a
> copy-on-read operation somehow (through a variable that stashes the
> base away somewhere?).
You don't even have to look at the implementation to say that COR is a
useful optimisation. It basically means that you reuse data read by the
guest instead of reading it a second time in your loop. (And this is
equally true for block copy and image streaming)
If this means adding a new field in BlockDriverState, so be it.
Kevin
next prev parent reply other threads:[~2011-06-30 12:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 14:32 [Qemu-devel] KVM call agenda for June 28 Juan Quintela
2011-06-28 13:38 ` Stefan Hajnoczi
2011-06-28 19:41 ` Marcelo Tosatti
2011-06-29 5:32 ` Stefan Hajnoczi
2011-06-29 7:57 ` Kevin Wolf
2011-06-29 10:08 ` Stefan Hajnoczi
2011-06-29 15:41 ` Marcelo Tosatti
2011-06-30 11:48 ` Stefan Hajnoczi
2011-06-30 12:39 ` Kevin Wolf [this message]
2011-06-30 12:54 ` Stefan Hajnoczi
2011-06-30 14:36 ` Marcelo Tosatti
2011-06-30 14:52 ` Kevin Wolf
2011-06-30 18:38 ` Marcelo Tosatti
2011-07-05 8:01 ` Dor Laor
2011-07-05 12:40 ` Stefan Hajnoczi
2011-07-05 12:58 ` Marcelo Tosatti
2011-07-05 13:39 ` Dor Laor
2011-07-05 14:29 ` Marcelo Tosatti
2011-07-05 14:32 ` Marcelo Tosatti
2011-07-05 14:46 ` Kevin Wolf
2011-07-05 15:04 ` Dor Laor
2011-07-05 15:29 ` Marcelo Tosatti
2011-07-05 15:37 ` Stefan Hajnoczi
2011-07-05 18:18 ` Marcelo Tosatti
2011-07-06 7:48 ` Kevin Wolf
2011-07-07 15:25 ` Stefan Hajnoczi
2011-06-28 13:43 ` Anthony Liguori
2011-06-28 13:48 ` Avi Kivity
2011-06-30 14:10 ` Anthony Liguori
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=4E0C6E8D.9040705@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).