From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Fam Zheng <fam@euphon.net>, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 3/3] aio-posix: keep aio_notify_me disabled during polling
Date: Tue, 4 Aug 2020 18:53:09 +0200 [thread overview]
Message-ID: <92e8cc23-a361-f1d4-a2a6-160268cd8b3a@redhat.com> (raw)
In-Reply-To: <20200804102941.GB1284284@stefanha-x1.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 2921 bytes --]
On 04/08/20 12:29, Stefan Hajnoczi wrote:
> On Tue, Aug 04, 2020 at 06:28:04AM +0100, Stefan Hajnoczi wrote:
>> @@ -597,15 +574,38 @@ bool aio_poll(AioContext *ctx, bool blocking)
>> * system call---a single round of run_poll_handlers_once suffices.
>> */
>> if (timeout || ctx->fdmon_ops->need_wait(ctx)) {
>> + /*
>> + * aio_notify can avoid the expensive event_notifier_set if
>> + * everything (file descriptors, bottom halves, timers) will
>> + * be re-evaluated before the next blocking poll(). This is
>> + * already true when aio_poll is called with blocking == false;
>> + * if blocking == true, it is only true after poll() returns,
>> + * so disable the optimization now.
>> + */
>> + if (timeout) {
>> + atomic_set(&ctx->notify_me, atomic_read(&ctx->notify_me) + 2);
>> + /*
>> + * Write ctx->notify_me before computing the timeout
>> + * (reading bottom half flags, etc.). Pairs with
>> + * smp_mb in aio_notify().
>> + */
>> + smp_mb();
>> +
>> + /* Check again in case a shorter timer was added */
>> + timeout = qemu_soonest_timeout(timeout, aio_compute_timeout(ctx));
>> + }
>> +
>> ret = ctx->fdmon_ops->wait(ctx, &ready_list, timeout);
>> - }
>>
>> - if (blocking) {
>> - /* Finish the poll before clearing the flag. */
>> - atomic_store_release(&ctx->notify_me, atomic_read(&ctx->notify_me) - 2);
>> - aio_notify_accept(ctx);
>> + if (timeout) {
>> + /* Finish the poll before clearing the flag. */
>> + atomic_store_release(&ctx->notify_me,
>> + atomic_read(&ctx->notify_me) - 2);
>> + }
>> }
>
> Hi Paolo,
> We can avoid calling aio_compute_timeout() like this, what do you think?
I don't understand :) except I guess you mean we can avoid the second
call. Can you post either a complete patch with this squashed, or a 4th
patch (whatever you think is best)?
Paolo
> bool use_notify_me = timeout != 0;
>
> if (use_notify_me) {
> atomic_set(&ctx->notify_me, atomic_read(&ctx->notify_me) + 2);
> /*
> * Write ctx->notify_me before computing the timeout
> * (reading bottom half flags, etc.). Pairs with
> * smp_mb in aio_notify().
> */
> smp_mb();
>
> /* Don't block if aio_notify() was called */
> if (atomic_read(ctx->notified)) {
> timeout = 0;
> }
> }
>
> ret = ctx->fdmon_ops->wait(ctx, &ready_list, timeout);
>
> if (use_notify_me) {
> /* Finish the poll before clearing the flag. */
> atomic_store_release(&ctx->notify_me,
> atomic_read(&ctx->notify_me) - 2);
> }
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-04 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 5:28 [PATCH 0/3] aio-posix: keep aio_notify_me disabled during polling Stefan Hajnoczi
2020-08-04 5:28 ` [PATCH 1/3] async: rename event_notifier_dummy_cb/poll() Stefan Hajnoczi
2020-08-04 5:28 ` [PATCH 2/3] async: always set ctx->notified in aio_notify() Stefan Hajnoczi
2020-08-04 7:12 ` Paolo Bonzini
2020-08-04 10:23 ` Stefan Hajnoczi
2020-08-04 5:28 ` [PATCH 3/3] aio-posix: keep aio_notify_me disabled during polling Stefan Hajnoczi
2020-08-04 10:29 ` Stefan Hajnoczi
2020-08-04 16:53 ` Paolo Bonzini [this message]
2020-08-05 8:59 ` Stefan Hajnoczi
2020-08-04 7:13 ` [PATCH 0/3] " Paolo Bonzini
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=92e8cc23-a361-f1d4-a2a6-160268cd8b3a@redhat.com \
--to=pbonzini@redhat.com \
--cc=fam@euphon.net \
--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).