From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, Karl Rister <krister@redhat.com>,
Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 09/10] aio: add .io_poll_begin/end() callbacks
Date: Tue, 22 Nov 2016 18:21:24 +0100 [thread overview]
Message-ID: <e2085f33-351d-f413-b8c7-577e8faaf474@redhat.com> (raw)
In-Reply-To: <1479832306-26440-10-git-send-email-stefanha@redhat.com>
On 22/11/2016 17:31, Stefan Hajnoczi wrote:
> +static bool try_poll_mode(AioContext *ctx, bool enable)
> +{
> + if (enable && aio_poll_max_ns && ctx->poll_disable_cnt == 0) {
> + /* See qemu_soonest_timeout() uint64_t hack */
> + int64_t max_ns = MIN((uint64_t)aio_compute_timeout(ctx),
> + (uint64_t)aio_poll_max_ns);
> +
> + if (max_ns) {
> + poll_set_started(ctx, true);
> +
> + if (run_poll_handlers(ctx, max_ns)) {
> + return true;
> + }
> + }
> + }
> +
> + poll_set_started(ctx, false);
You could do a single iteration even if enable == false (which I'd
rename to blocking, BTW, because poll_start can be false on exit even if
enable == true).
In fact, since (like virtio_queue_host_notifier_aio_poll_end) all
.io_poll_end() callbacks are going to poll once more, what about adding
here:
return run_poll_handlers(ctx, 0);
or just an instance of the loop, without qemu_clock_get_ns and the
tracepoints:
return run_poll_handlers_once(ctx);
and removing from patch 10 the
/* Handle any buffers that snuck in after we finished polling */
virtio_queue_host_notifier_aio_poll(n);
?
Thanks,
Paolo
next prev parent reply other threads:[~2016-11-22 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 16:31 [Qemu-devel] [PATCH v3 00/10] aio: experimental virtio-blk polling mode Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 01/10] virtio: add missing vdev->broken check Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 02/10] virtio-blk: suppress virtqueue kick during processing Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 03/10] virtio-scsi: " Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 04/10] aio: add AioPollFn and io_poll() interface Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 05/10] aio: add polling mode to AioContext Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 06/10] virtio: poll virtqueues for new buffers Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 07/10] linux-aio: poll ring for completions Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 08/10] virtio: turn vq->notification into a nested counter Stefan Hajnoczi
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 09/10] aio: add .io_poll_begin/end() callbacks Stefan Hajnoczi
2016-11-22 17:21 ` Paolo Bonzini [this message]
2016-11-23 9:44 ` Stefan Hajnoczi
2016-11-23 10:59 ` Paolo Bonzini
2016-11-22 16:31 ` [Qemu-devel] [PATCH v3 10/10] virtio: disable virtqueue notifications during polling Stefan Hajnoczi
2016-11-22 16:57 ` [Qemu-devel] [PATCH v3 00/10] aio: experimental virtio-blk polling mode no-reply
2016-11-22 17:13 ` Paolo Bonzini
2016-11-22 19:21 ` Christian Borntraeger
2016-11-23 9:51 ` 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=e2085f33-351d-f413-b8c7-577e8faaf474@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=famz@redhat.com \
--cc=krister@redhat.com \
--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).