From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Fam Zheng <fam@euphon.net>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org, Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [PATCH 3/4] qemu-io: add -r option to register I/O buffer
Date: Fri, 27 Jan 2023 17:24:30 -0600 [thread overview]
Message-ID: <20230127232430.zy7x7wq2dvb3g3y2@redhat.com> (raw)
In-Reply-To: <20230126201401.348845-4-stefanha@redhat.com>
On Thu, Jan 26, 2023 at 03:14:00PM -0500, Stefan Hajnoczi wrote:
> The blk_register_buf() API is an optimization hint that allows some
> block drivers to avoid I/O buffer housekeeping or bounce buffers.
>
> Add an -r option to register the I/O buffer so that qemu-io can be used
> to test the blk_register_buf() API. The next commit will add a test that
> uses the new option.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> qemu-io-cmds.c | 149 ++++++++++++++++++++++++++++++++++---------------
> 1 file changed, 103 insertions(+), 46 deletions(-)
>
> static void *qemu_io_alloc_from_file(BlockBackend *blk, size_t len,
> - const char *file_name)
> + const char *file_name, bool register_buf)
> {
> char *buf, *buf_origin;
> FILE *f = fopen(file_name, "r");
> @@ -414,6 +423,10 @@ static void *qemu_io_alloc_from_file(BlockBackend *blk, size_t len,
> fclose(f);
> f = NULL;
>
> + if (register_buf) {
> + blk_register_buf(blk, buf_origin, len, &error_abort);
> + }
Why is this conditionally true...
> +
> if (len > pattern_len) {
> len -= pattern_len;
> buf += pattern_len;
> @@ -431,7 +444,7 @@ static void *qemu_io_alloc_from_file(BlockBackend *blk, size_t len,
> return buf_origin;
>
> error:
> - qemu_io_free(buf_origin);
> + qemu_io_free(blk, buf_origin, len, false);
...but cleanup unconditionally false?
> @@ -719,6 +732,7 @@ static void read_help(void)
> " -p, -- ignored for backwards compatibility\n"
> " -P, -- use a pattern to verify read data\n"
> " -q, -- quiet mode, do not show I/O statistics\n"
> +" -r, -- register I/O buffer\n"
> " -s, -- start offset for pattern verification (only with -P)\n"
> " -v, -- dump buffer to standard output\n"
Here we have kept more or less alphabetical...
> @@ -909,6 +932,7 @@ static void readv_help(void)
> " -P, -- use a pattern to verify read data\n"
> " -v, -- dump buffer to standard output\n"
> " -q, -- quiet mode, do not show I/O statistics\n"
> +" -r, -- register I/O buffer\n"
...here we have not. While it's pre-existing, would it be worth
touching up while you're here?
> @@ -1455,6 +1503,7 @@ static void aio_read_help(void)
> " -i, -- treat request as invalid, for exercising stats\n"
> " -v, -- dump buffer to standard output\n"
> " -q, -- quiet mode, do not show I/O statistics\n"
> +" -r, -- register I/O buffer\n"
Another pre-existing spot.
Overall makes sense to me.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2023-01-27 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 20:13 [PATCH 0/4] block: fix detect-zeroes= with BDRV_REQ_REGISTERED_BUF Stefan Hajnoczi
2023-01-26 20:13 ` [PATCH 1/4] " Stefan Hajnoczi
2023-01-27 8:23 ` Fiona Ebner
2023-01-26 20:13 ` [PATCH 2/4] qemu-io: use BdrvRequestFlags instead of int Stefan Hajnoczi
2023-01-27 23:18 ` Eric Blake
2023-01-26 20:14 ` [PATCH 3/4] qemu-io: add -r option to register I/O buffer Stefan Hajnoczi
2023-01-27 23:24 ` Eric Blake [this message]
2023-01-30 20:55 ` Stefan Hajnoczi
2023-01-26 20:14 ` [PATCH 4/4] iotests/detect-zeroes-registered-buf: add new test Stefan Hajnoczi
2023-01-27 23:25 ` Eric Blake
2023-01-30 20:46 ` Stefan Hajnoczi
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=20230127232430.zy7x7wq2dvb3g3y2@redhat.com \
--to=eblake@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).