On Fri, 04/06 13:41, Paolo Bonzini wrote:
> On 05/04/2018 14:55, Stefan Hajnoczi wrote:
> > bdrv_copy_file_range() will invoke bdrv_co_copy_file_range_src() on
> > src[qcow2]. The qcow2 block driver will invoke
> > bdrv_co_copy_file_range_src() on src[file]. The file-posix driver will
> > invoke
On 05/04/2018 14:55, Stefan Hajnoczi wrote:
> bdrv_copy_file_range() will invoke bdrv_co_copy_file_range_src() on
> src[qcow2]. The qcow2 block driver will invoke
> bdrv_co_copy_file_range_src() on src[file]. The file-posix driver will
> invoke bdrv_co_copy_file_range_dst() on dst[raw]. The raw
On Wed, Apr 04, 2018 at 09:49:23PM +0800, Fam Zheng wrote:
> On Wed, 04/04 14:23, Stefan Hajnoczi wrote:
> > On Thu, Mar 29, 2018 at 07:09:06PM +0800, Fam Zheng wrote:
> > > [Posting a preview RFC for the general idea discussion and internal API
> > > review.
> > > Libiscsi support is being
On 04/04/2018 15:49, Fam Zheng wrote:
>> I posted concerns about the bdrv_co_map_range() interface. It would be
>> safer to only have a copy_range() interface without exposing how data is
>> mapped outside the driver where race conditions can occur and the format
>> driver no longer has full
On Wed, 04/04 14:23, Stefan Hajnoczi wrote:
> On Thu, Mar 29, 2018 at 07:09:06PM +0800, Fam Zheng wrote:
> > [Posting a preview RFC for the general idea discussion and internal API
> > review.
> > Libiscsi support is being worked on in the meantime.]
> >
> > This series introduces block layer
On Thu, Mar 29, 2018 at 07:09:06PM +0800, Fam Zheng wrote:
> [Posting a preview RFC for the general idea discussion and internal API
> review.
> Libiscsi support is being worked on in the meantime.]
>
> This series introduces block layer API for copy offloading and makes use of it
> in qemu-img
