From: Zhenyu Ye <yezhenyu2@huawei.com>
To: Kevin Wolf <kwolf@redhat.com>, <mreitz@redhat.com>,
<qemu-block@nongnu.org>, <qemu-devel@nongnu.org>, <pl@kamp.de>
Subject: [Question] qemu-img convert block alignment
Date: Fri, 2 Apr 2021 11:52:25 +0800 [thread overview]
Message-ID: <ed4ae175-1c67-b7fb-669d-c8c08ca1a7f7@huawei.com> (raw)
Hi all,
commit 8dcd3c9b91 ("qemu-img: align result of is_allocated_sectors")
introduces block alignment when doing qemu-img convert. However, the
alignment is:
s.alignment = MAX(pow2floor(s.min_sparse),
DIV_ROUND_UP(out_bs->bl.request_alignment,
BDRV_SECTOR_SIZE));
(where the default s.min_sparse is 8)
When the target device's bl.request_alignment is smaller than 4K, this
will cause additional write-zero overhead and makes the size of target
file larger.
Is this as expected? Should we change the MAX() to MIN()?
Thanks,
zhenyu
next reply other threads:[~2021-04-02 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 3:52 Zhenyu Ye [this message]
2021-08-03 1:53 ` [Question] qemu-img convert block alignment Zhenyu Ye
2021-08-03 15:03 ` Eric Blake
2021-08-04 7:18 ` Zhenyu Ye
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=ed4ae175-1c67-b7fb-669d-c8c08ca1a7f7@huawei.com \
--to=yezhenyu2@huawei.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).