[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Choice of BDRV_REQUEST_MAX_SECTORS
From: |
Eric Blake |
Subject: |
Re: Choice of BDRV_REQUEST_MAX_SECTORS |
Date: |
Mon, 17 Aug 2020 08:44:17 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 |
On 8/17/20 7:32 AM, Peter Lieven wrote:
Hi,
I am currently debugging a performance issue in qemu-img convert. I
think I have found the cause and will send a patch later.
But is there any reason why BDRV_REQUEST_MAX_SECTORS is not at least
aligned down to 8 (4k sectors)?
Any operation that is not able to determinate an optimal or maximum
request size from a driver will likely use this value and
might generate unaligned requests (as qemu-img convert does) as soon as
the first iteration of an operation is done.
Vladimir's work to make the block layer 64-bit clean should help resolve
this, as we will be relying more heavily on values aligned to the
driver's limits rather than arbitrary 32-bit cutoffs.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org