qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 2/3] linux-aio: handling -EAGAIN for !s->io_q.plugged case
Date: Mon, 24 Nov 2014 18:58:39 +0000	[thread overview]
Message-ID: <20141124185839.GB14760@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1416839379-19677-3-git-send-email-ming.lei@canonical.com>

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

On Mon, Nov 24, 2014 at 10:29:38PM +0800, Ming Lei wrote:
> Previously -EAGAIN is simply ignored for !s->io_q.plugged case,
> and sometimes it is easy to cause -EIO to VM, such as NVME device.
> 
> This patch handles -EAGAIN by io queue for !s->io_q.plugged case,
> and it will be retried in following aio completion cb.
> 
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Ming Lei <ming.lei@canonical.com>
> ---
>  block/linux-aio.c |   28 ++++++++++++++++++----------
>  1 file changed, 18 insertions(+), 10 deletions(-)
> 
> diff --git a/block/linux-aio.c b/block/linux-aio.c
> index 70312a4..0cb098d 100644
> --- a/block/linux-aio.c
> +++ b/block/linux-aio.c
> @@ -282,12 +282,17 @@ static int ioq_enqueue(struct qemu_laio_state *s, struct iocb *iocb)
>      s->io_q.iocbs[idx++] = iocb;
>      s->io_q.idx = idx;
>  
> -    /* submit immediately if queue depth is above 2/3 */
> -    if (idx > s->io_q.size * 2 / 3) {
> -        return ioq_submit(s);
> +    /*
> +     * This is reached in two cases: queue not plugged but io_submit
> +     * returned -EAGAIN, or queue plugged.  In the latter case, start
> +     * submitting some I/O if the queue is getting too full.  In the
> +     * former case, instead, wait until an I/O operation is completed.
> +     */
> +    if (!s->io_q.plugged || likely(idx < s->io_q.size * 2 / 3)) {
> +        return 0;
>      }
>  
> -    return 0;
> +    return ioq_submit(s);

Same as in the previous patch, the ioq_submit() return value is not
meaningful to ioq_enqueue() callers.  It should not be returned.

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-11-24 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:29 [Qemu-devel] [PATCH v5 0/3] linux-aio: fix batch submission Ming Lei
2014-11-24 14:29 ` [Qemu-devel] [PATCH v5 1/3] linux-aio: fix submit aio as a batch Ming Lei
2014-11-24 16:40   ` Stefan Hajnoczi
2014-11-24 19:01   ` Stefan Hajnoczi
2014-11-24 14:29 ` [Qemu-devel] [PATCH v5 2/3] linux-aio: handling -EAGAIN for !s->io_q.plugged case Ming Lei
2014-11-24 18:58   ` Stefan Hajnoczi [this message]
2014-11-24 14:29 ` [Qemu-devel] [PATCH v5 3/3] linux-aio: remove 'node' from 'struct qemu_laiocb' Ming Lei
2014-11-24 14:31 ` [Qemu-devel] [PATCH v5 0/3] linux-aio: fix batch submission Paolo Bonzini
2014-11-24 14:50   ` Ming Lei

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=20141124185839.GB14760@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=ming.lei@canonical.com \
    --cc=pbonzini@redhat.com \
    --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).