From: Kevin Wolf <kwolf@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH 4/4] block/file: Add file-specific image info
Date: Wed, 4 May 2022 10:46:21 +0200 [thread overview]
Message-ID: <YnI9XZkxiNNJX3dC@redhat.com> (raw)
In-Reply-To: <20220503145529.37070-5-hreitz@redhat.com>
Am 03.05.2022 um 16:55 hat Hanna Reitz geschrieben:
> Add some (optional) information that the file driver can provide for
> image files, namely the extent size.
>
> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
> ---
> qapi/block-core.json | 26 ++++++++++++++++++++++++--
> block/file-posix.c | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 54 insertions(+), 2 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index e7d6c2e0cc..728da051ae 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -139,16 +139,29 @@
> '*encryption-format': 'RbdImageEncryptionFormat'
> } }
>
> +##
> +# @ImageInfoSpecificFile:
> +#
> +# @extent-size: Extent size (if available)
> +#
> +# Since: 7.1
> +##
> +{ 'struct': 'ImageInfoSpecificFile',
> + 'data': {
> + '*extent-size': 'size'
> + } }
It's not "the extent size" (the whole point of extents is that they
don't have a fixed size like blocks), but an extent size *hint* that
tells the filesystem the minimum size to allocate for an extent. The
xfs_io man page calls it the preferred extent size for allocatino, which
works for the documentation if you prefer, but BlockdevCreateOptionsFile
has 'extent-size-hint', so I'd prefer consistency on the wire at least.
Kevin
next prev parent reply other threads:[~2022-05-04 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:55 [PATCH 0/4] block/file: Show extent size in qemu-img info Hanna Reitz
2022-05-03 14:55 ` [PATCH 1/4] block: Improve empty format-specific info dump Hanna Reitz
2022-05-03 18:44 ` Eric Blake
2022-05-04 8:18 ` Kevin Wolf
2022-05-03 14:55 ` [PATCH 2/4] block: Add protocol-specific image info Hanna Reitz
2022-05-03 18:47 ` Eric Blake
2022-05-04 8:36 ` Kevin Wolf
2022-05-04 11:25 ` Hanna Reitz
2022-05-03 14:55 ` [PATCH 3/4] block: Print protocol-specific information Hanna Reitz
2022-05-03 18:48 ` Eric Blake
2022-05-03 14:55 ` [PATCH 4/4] block/file: Add file-specific image info Hanna Reitz
2022-05-03 18:50 ` Eric Blake
2022-05-04 7:10 ` Hanna Reitz
2022-05-04 8:46 ` Kevin Wolf [this message]
2022-05-04 11:26 ` Hanna Reitz
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=YnI9XZkxiNNJX3dC@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--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).