All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	qemu-block@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 2/3] iothread: add aio-max-batch parameter
Date: Tue, 13 Jul 2021 15:51:15 +0100	[thread overview]
Message-ID: <YO2oY/OObOC9Io1e@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210707150019.201442-3-sgarzare@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

On Wed, Jul 07, 2021 at 05:00:18PM +0200, Stefano Garzarella wrote:
> diff --git a/qapi/misc.json b/qapi/misc.json
> index 156f98203e..f64bb69f74 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -86,6 +86,9 @@
>  # @poll-shrink: how many ns will be removed from polling time, 0 means that
>  #               it's not configured (since 2.9)
>  #
> +# @aio-max-batch: maximum number of requests in a bacth for the AIO engine,

s/bacth/batch/

> +#                 0 means that the engine will use its default (since 6.1)
> +#
>  # Since: 2.0
>  ##
>  { 'struct': 'IOThreadInfo',
> @@ -93,7 +96,8 @@
>             'thread-id': 'int',
>             'poll-max-ns': 'int',
>             'poll-grow': 'int',
> -           'poll-shrink': 'int' } }
> +           'poll-shrink': 'int',
> +           'aio-max-batch': 'int' } }
>  
>  ##
>  # @query-iothreads:
> diff --git a/qapi/qom.json b/qapi/qom.json
> index 652be317b8..23fd586614 100644
> --- a/qapi/qom.json
> +++ b/qapi/qom.json
> @@ -516,12 +516,17 @@
>  #               algorithm detects it is spending too long polling without
>  #               encountering events. 0 selects a default behaviour (default: 0)
>  #
> +# @aio-max-batch: maximum number of requests in a bacth for the AIO engine,

s/bacth/batch/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-07-13 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 15:00 [PATCH 0/3] linux-aio: limit the batch size to reduce queue latency Stefano Garzarella
2021-07-07 15:00 ` [PATCH 1/3] iothread: generalize iothread_set_param/iothread_get_param Stefano Garzarella
2021-07-07 15:00 ` [PATCH 2/3] iothread: add aio-max-batch parameter Stefano Garzarella
2021-07-13 14:51   ` Stefan Hajnoczi [this message]
2021-07-19 10:10     ` Stefano Garzarella
2021-07-07 15:00 ` [PATCH 3/3] linux-aio: limit the batch size using `aio-max-batch` parameter Stefano Garzarella
2021-07-13 14:58   ` Stefan Hajnoczi
2021-07-19 10:35     ` Stefano Garzarella
2021-07-20 10:41       ` 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=YO2oY/OObOC9Io1e@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.