Am 22.03.2019 um 14:21 hat Kevin Wolf geschrieben:
> If qemu-img convert sees that the target image isn't zero-initialised
> yet, it tries to do an efficient zero write for the whole image first
> to save the overhead of repeated explicit zero writes during the
> conversion. Obviously, this
On Fri, Mar 22, 2019 at 10:47 PM Eric Blake wrote:
> On 3/22/19 3:22 PM, Nir Soffer wrote:
>
> > Thanks for fixing this! This will be a very important performance fix for
> > importing
> > VMs.
> >
> > The change description sounds good to me.
> >
> > Can you make these patches available on some
On 3/22/19 3:22 PM, Nir Soffer wrote:
> Thanks for fixing this! This will be a very important performance fix for
> importing
> VMs.
>
> The change description sounds good to me.
>
> Can you make these patches available on some git repo to make it easy to
> test?
Based on commit titles, this
On Fri, Mar 22, 2019 at 3:22 PM Kevin Wolf wrote:
> If qemu-img convert sees that the target image isn't zero-initialised
> yet, it tries to do an efficient zero write for the whole image first
> to save the overhead of repeated explicit zero writes during the
> conversion. Obviously, this
On 3/22/19 8:21 AM, Kevin Wolf wrote:
> If qemu-img convert sees that the target image isn't zero-initialised
> yet, it tries to do an efficient zero write for the whole image first
> to save the overhead of repeated explicit zero writes during the
> conversion. Obviously, this provides only an
If qemu-img convert sees that the target image isn't zero-initialised
yet, it tries to do an efficient zero write for the whole image first
to save the overhead of repeated explicit zero writes during the
conversion. Obviously, this provides only an advantage if the
pre-zeroing is actually
