From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Fam Zheng <fam@euphon.net>, Fiona Ebner <f.ebner@proxmox.com>,
Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [PATCH v2 3/4] qemu-io: add -r option to register I/O buffer
Date: Tue, 31 Jan 2023 15:23:24 -0600 [thread overview]
Message-ID: <20230131212324.4btboq2utna6hx3w@redhat.com> (raw)
In-Reply-To: <20230130215415.919494-4-stefanha@redhat.com>
On Mon, Jan 30, 2023 at 04:54:14PM -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 | 167 +++++++++++++++++++++++++++++++++----------------
> 1 file changed, 114 insertions(+), 53 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
> @@ -1277,7 +1322,7 @@ static int writev_f(BlockBackend *blk, int argc, char **argv)
> int pattern = 0xcd;
> QEMUIOVector qiov;
>
> - while ((c = getopt(argc, argv, "CfqP:")) != -1) {
> + while ((c = getopt(argc, argv, "CfqrP:")) != -1) {
This one is still odd - it is neither case-sensitive nor
case-insensitive in order, because of P: coming after qr.
> @@ -1476,7 +1529,7 @@ static int aio_read_f(BlockBackend *blk, int argc, char **argv)
> struct aio_ctx *ctx = g_new0(struct aio_ctx, 1);
>
> ctx->blk = blk;
> - while ((c = getopt(argc, argv, "CP:iqv")) != -1) {
> + while ((c = getopt(argc, argv, "CP:iqrv")) != -1) {
This one could at least argue that all capitals are before any
lower-case, although case-insensitive would put i before P:.
> @@ -1582,22 +1641,24 @@ static int aio_write_f(BlockBackend *blk, int argc, char **argv)
> int nr_iov, c;
> int pattern = 0xcd;
> struct aio_ctx *ctx = g_new0(struct aio_ctx, 1);
> - BdrvRequestFlags flags = 0;
>
> ctx->blk = blk;
> - while ((c = getopt(argc, argv, "CfiqP:uz")) != -1) {
> + while ((c = getopt(argc, argv, "CfiqrP:uz")) != -1) {
Another odd spot where P: would fit better before qr.
Those are still minor, so I don't care if you further touch them
up. My R-b applies either way.
--
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-31 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 21:54 [PATCH v2 0/4] block: fix detect-zeroes= with BDRV_REQ_REGISTERED_BUF Stefan Hajnoczi
2023-01-30 21:54 ` [PATCH v2 1/4] " Stefan Hajnoczi
2023-01-31 20:36 ` Eric Blake
2023-01-30 21:54 ` [PATCH v2 2/4] qemu-io: use BdrvRequestFlags instead of int Stefan Hajnoczi
2023-01-30 21:54 ` [PATCH v2 3/4] qemu-io: add -r option to register I/O buffer Stefan Hajnoczi
2023-01-31 21:23 ` Eric Blake [this message]
2023-02-01 14:49 ` Stefan Hajnoczi
2023-01-30 21:54 ` [PATCH v2 4/4] iotests/detect-zeroes-registered-buf: add new test 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=20230131212324.4btboq2utna6hx3w@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).