qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Fam Zheng <fam@euphon.net>
Subject: Re: [RFC 0/3] aio-posix: call ->poll_end() when removing AioHandler
Date: Tue, 23 Jan 2024 12:25:20 +0100	[thread overview]
Message-ID: <b609e36e-62ab-40d0-b51a-3717f90a51e5@redhat.com> (raw)
In-Reply-To: <8a32f350-e69a-458a-be4e-1d3335e696c6@proxmox.com>

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

On 23.01.24 12:12, Fiona Ebner wrote:

[...]

> I noticed poll_set_started() is not called, because
> ctx->fdmon_ops->need_wait(ctx) was true, i.e. ctx->poll_disable_cnt was
> positive (I'm using fdmon_poll). I then found this is because of the
> notifier for the event vq, being attached with
>
>> virtio_queue_aio_attach_host_notifier_no_poll(vs->event_vq, s->ctx);
> in virtio_scsi_dataplane_start(). But in virtio_scsi_drained_end() it is
> attached with virtio_queue_aio_attach_host_notifier() instead of the
> _no_poll() variant. So that might be the actual issue here?
>
>  From a quick test, I cannot see the CPU-usage-spike issue with the
> following either:
>
>> diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
>> index 690aceec45..ba1ab8e410 100644
>> --- a/hw/scsi/virtio-scsi.c
>> +++ b/hw/scsi/virtio-scsi.c
>> @@ -1166,7 +1166,15 @@ static void virtio_scsi_drained_end(SCSIBus *bus)
>>   
>>       for (uint32_t i = 0; i < total_queues; i++) {
>>           VirtQueue *vq = virtio_get_queue(vdev, i);
>> -        virtio_queue_aio_attach_host_notifier(vq, s->ctx);
>> +        if (!virtio_queue_get_notification(vq)) {
>> +            virtio_queue_set_notification(vq, true);
>> +        }
>> +        if (vq == VIRTIO_SCSI_COMMON(s)->event_vq) {
>> +            virtio_queue_aio_attach_host_notifier_no_poll(vq, s->ctx);
>> +        } else {
>> +            virtio_queue_aio_attach_host_notifier(vq, s->ctx);
>> +        }
>> +        virtio_queue_notify(vdev, i);
>>       }
>>   }

Perfect, so we agree on trying it that way. :)

Hanna

[-- Attachment #2: Type: text/html, Size: 2216 bytes --]

  reply	other threads:[~2024-01-23 11:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 21:15 [RFC 0/3] aio-posix: call ->poll_end() when removing AioHandler Stefan Hajnoczi
2023-12-13 21:15 ` [RFC 1/3] aio-posix: run aio_set_fd_handler() in target AioContext Stefan Hajnoczi
2023-12-13 21:15 ` [RFC 2/3] aio: use counter instead of ctx->list_lock Stefan Hajnoczi
2023-12-13 21:15 ` [RFC 3/3] aio-posix: call ->poll_end() when removing AioHandler Stefan Hajnoczi
2023-12-13 21:52   ` Paolo Bonzini
2023-12-14 20:12     ` Stefan Hajnoczi
2023-12-14 20:39       ` Paolo Bonzini
2023-12-18 14:27         ` Stefan Hajnoczi
2023-12-13 21:52 ` [RFC 0/3] " Stefan Hajnoczi
2023-12-13 23:10 ` Paolo Bonzini
2023-12-14 19:52   ` Stefan Hajnoczi
2023-12-14 13:38 ` Fiona Ebner
2023-12-14 19:53   ` Stefan Hajnoczi
2023-12-18 12:41     ` Fiona Ebner
2023-12-18 14:25       ` Stefan Hajnoczi
2023-12-18 14:49       ` Paolo Bonzini
2023-12-19  8:40         ` Fiona Ebner
2024-01-02 15:24 ` Hanna Czenczek
2024-01-02 15:53   ` Paolo Bonzini
2024-01-02 16:55     ` Hanna Czenczek
2024-01-03 11:40   ` Fiona Ebner
2024-01-03 13:35     ` Paolo Bonzini
2024-01-05 13:43       ` Fiona Ebner
2024-01-05 14:30         ` Fiona Ebner
2024-01-22 17:41           ` Hanna Czenczek
2024-01-22 17:52             ` Hanna Czenczek
2024-01-23 11:12               ` Fiona Ebner
2024-01-23 11:25                 ` Hanna Czenczek [this message]
2024-01-23 11:15               ` Hanna Czenczek
2024-01-23 16:28   ` Hanna Czenczek

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=b609e36e-62ab-40d0-b51a-3717f90a51e5@redhat.com \
    --to=hreitz@redhat.com \
    --cc=f.ebner@proxmox.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@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).