Re: [Qemu-block] [PATCH V4] qemu-img: align result of is_allocated_sectors

2018-07-10 Thread Kevin Wolf
Am 10.07.2018 um 14:36 hat Peter Lieven geschrieben: > Am 10.07.2018 um 14:28 schrieb Kevin Wolf: > > Am 07.07.2018 um 13:42 hat Peter Lieven geschrieben: > > > We currently don't enforce that the sparse segments we detect during > > > convert are > > > aligned. This leads to unnecessary and

Re: [Qemu-block] [PATCH V4] qemu-img: align result of is_allocated_sectors

2018-07-10 Thread Peter Lieven
Am 10.07.2018 um 14:28 schrieb Kevin Wolf: Am 07.07.2018 um 13:42 hat Peter Lieven geschrieben: We currently don't enforce that the sparse segments we detect during convert are aligned. This leads to unnecessary and costly read-modify-write cycles either internally in Qemu or in the background

Re: [Qemu-block] [PATCH V4] qemu-img: align result of is_allocated_sectors

2018-07-10 Thread Kevin Wolf
Am 07.07.2018 um 13:42 hat Peter Lieven geschrieben: > We currently don't enforce that the sparse segments we detect during convert > are > aligned. This leads to unnecessary and costly read-modify-write cycles either > internally in Qemu or in the background on the storage device as nearly all >

[Qemu-block] [PATCH V4] qemu-img: align result of is_allocated_sectors

2018-07-07 Thread Peter Lieven
We currently don't enforce that the sparse segments we detect during convert are aligned. This leads to unnecessary and costly read-modify-write cycles either internally in Qemu or in the background on the storage device as nearly all modern filesystems or hardware have a 4k alignment internally.