aboutsummaryrefslogtreecommitdiff
path: root/util/bitmap.c
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2020-02-21 09:39:51 +0000
committerStefan Hajnoczi <stefanha@redhat.com>2020-02-22 08:26:47 +0000
commit8c6b0356b53977bcfdea5299db07884915425b0c (patch)
treed309eb193c9a185cd2c9a58bcc769ffb73b108c7 /util/bitmap.c
parent8c3570e33954d26675ec6fd224ede02763dfbd1d (diff)
downloadqemu-8c6b0356b53977bcfdea5299db07884915425b0c.zip
qemu-8c6b0356b53977bcfdea5299db07884915425b0c.tar.gz
qemu-8c6b0356b53977bcfdea5299db07884915425b0c.tar.bz2
util/async: make bh_aio_poll() O(1)
The ctx->first_bh list contains all created BHs, including those that are not scheduled. The list is iterated by the event loop and therefore has O(n) time complexity with respected to the number of created BHs. Rewrite BHs so that only scheduled or deleted BHs are enqueued. Only BHs that actually require action will be iterated. One semantic change is required: qemu_bh_delete() enqueues the BH and therefore invokes aio_notify(). The tests/test-aio.c:test_source_bh_delete_from_cb() test case assumed that g_main_context_iteration(NULL, false) returns false after qemu_bh_delete() but it now returns true for one iteration. Fix up the test case. This patch makes aio_compute_timeout() and aio_bh_poll() drop from a CPU profile reported by perf-top(1). Previously they combined to 9% CPU utilization when AioContext polling is commented out and the guest has 2 virtio-blk,num-queues=1 and 99 virtio-blk,num-queues=32 devices. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Message-id: 20200221093951.1414693-1-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'util/bitmap.c')
0 files changed, 0 insertions, 0 deletions