From: Marcelo Tosatti <mtosatti@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
jes sorensen <jes.sorensen@redhat.com>,
Dor Laor <dlaor@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] Image streaming and live block copy (was: [PATCH 00/13] QED image streaming)
Date: Thu, 16 Jun 2011 11:55:43 -0300 [thread overview]
Message-ID: <20110616145543.GC12173@amt.cnet> (raw)
In-Reply-To: <20110616143848.GA12173@amt.cnet>
On Thu, Jun 16, 2011 at 11:38:48AM -0300, Marcelo Tosatti wrote:
> > People seem to agree on this, and the reason that I've heard why we
> > should merge the existing code instead is downstream time pressure. That
> > may be a valid reason for downstreams to add such code, but is taking
> > such code really the best option for upstream (and therefore long-term
> > for downstreams)?
> >
> > If we take these patches as they are, I doubt that we'll ever get a
> > rewrite to implement the code as it should have been done in the first
> > place.
>
> That (a newer, unified mechanism) is just a matter of allocating
> resources to the implementation.
>
> At least in block copy's case the interface can be reused, so it can be
> seen as an incremental approach (read: advocating in favour of merging
> live block copy patchset).
>
> > So I'm tempted to reject the current versions of both the image
> > streaming and live block copy series and leave it to downstreams to use
> > these as temporary solutions if the time pressure is too high. I know
> > that maintaining things downstream is painful, but that's the whole
> > point: I want to see the real implementation one day, and I'm afraid
> > this might be the only way to get it.
Again: there is no need to reject current live block copy
implementation, as image streaming implemented for generic image formats
is a strong motivator behind the unified implementation.
next prev parent reply other threads:[~2011-06-16 14:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:18 [Qemu-devel] [PATCH 00/13] QED image streaming Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 01/13] qemu-config: }, { -> }, { to please checkpatch.pl Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 02/13] block: add -drive copy-on-read=on|off Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 03/13] qed: replace is_write with flags field Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 04/13] qed: extract qed_start_allocating_write() Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 05/13] qed: make qed_aio_write_alloc() reusable Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 06/13] qed: add support for copy-on-read Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 07/13] qed: avoid deadlock on emulated synchronous I/O Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 08/13] qerror: add qerror_from_args() to create qerror objects Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 09/13] block: add bdrv_aio_copy_backing() Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 10/13] qmp: add QMP support for stream commands Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 11/13] block: add -drive stream=on|off Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 12/13] qed: intelligent streaming implementation Stefan Hajnoczi
2011-06-14 18:18 ` [Qemu-devel] [PATCH 13/13] trace: trace bdrv_aio_readv/writev error paths Stefan Hajnoczi
2011-06-15 10:46 ` [Qemu-devel] [PATCH 00/13] QED image streaming Philipp Hahn
2011-06-15 12:18 ` Stefan Hajnoczi
2011-06-16 12:35 ` [Qemu-devel] Image streaming and live block copy (was: [PATCH 00/13] QED image streaming) Kevin Wolf
2011-06-16 12:49 ` [Qemu-devel] Image streaming and live block copy Avi Kivity
2011-06-16 13:08 ` Kevin Wolf
2011-06-16 13:38 ` Avi Kivity
2011-06-16 14:52 ` Marcelo Tosatti
2011-06-16 15:30 ` Stefan Hajnoczi
2011-06-17 12:31 ` Marcelo Tosatti
2011-06-18 9:15 ` Stefan Hajnoczi
2011-06-18 9:17 ` Stefan Hajnoczi
2011-06-19 16:02 ` Dor Laor
2011-06-24 9:28 ` Stefan Hajnoczi
2011-06-26 12:50 ` Dor Laor
2011-06-27 7:48 ` Kevin Wolf
2011-06-27 9:13 ` Dor Laor
2011-06-17 13:54 ` Marcelo Tosatti
2011-06-17 8:36 ` Kevin Wolf
2011-06-17 8:57 ` Stefan Hajnoczi
2011-06-17 9:22 ` Kevin Wolf
2011-06-17 10:11 ` Stefan Hajnoczi
2011-06-17 12:21 ` Anthony Liguori
2011-06-17 13:04 ` Marcelo Tosatti
2011-06-17 13:50 ` Marcelo Tosatti
2011-06-16 13:10 ` Anthony Liguori
2011-06-16 13:50 ` Kevin Wolf
2011-06-16 14:38 ` [Qemu-devel] Image streaming and live block copy (was: [PATCH 00/13] QED image streaming) Marcelo Tosatti
2011-06-16 14:55 ` Marcelo Tosatti [this message]
2011-06-17 8:21 ` [Qemu-devel] Image streaming and live block copy Kevin Wolf
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=20110616145543.GC12173@amt.cnet \
--to=mtosatti@redhat.com \
--cc=agl@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=jes.sorensen@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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.