From: "manish.mishra" <manish.mishra@nutanix.com>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com, peterx@redhat.com, quintela@redhat.com,
dgilbert@redhat.com, lsoaresp@redhat.com,
"manish.mishra" <manish.mishra@nutanix.com>
Subject: [PATCH] multifd: Avoid busy-wait in multifd_send_pages()
Date: Tue, 25 Apr 2023 16:05:55 +0000 [thread overview]
Message-ID: <20230425160555.67373-1-manish.mishra@nutanix.com> (raw)
multifd_send_sync_main() posts request on the multifd channel
but does not call sem_wait() on channels_ready semaphore, making
the channels_ready semaphore count keep increasing.
As a result, sem_wait() on channels_ready in multifd_send_pages()
is always non-blocking hence multifd_send_pages() keeps searching
for a free channel in a busy loop until a channel is freed.
Signed-off-by: manish.mishra <manish.mishra@nutanix.com>
---
migration/multifd.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/migration/multifd.c b/migration/multifd.c
index cce3ad6988..43d26e7012 100644
--- a/migration/multifd.c
+++ b/migration/multifd.c
@@ -615,6 +615,7 @@ int multifd_send_sync_main(QEMUFile *f)
trace_multifd_send_sync_main_signal(p->id);
+ qemu_sem_wait(&multifd_send_state->channels_ready);
qemu_mutex_lock(&p->mutex);
if (p->quit) {
@@ -919,7 +920,7 @@ int multifd_save_setup(Error **errp)
multifd_send_state = g_malloc0(sizeof(*multifd_send_state));
multifd_send_state->params = g_new0(MultiFDSendParams, thread_count);
multifd_send_state->pages = multifd_pages_init(page_count);
- qemu_sem_init(&multifd_send_state->channels_ready, 0);
+ qemu_sem_init(&multifd_send_state->channels_ready, thread_count);
qatomic_set(&multifd_send_state->exiting, 0);
multifd_send_state->ops = multifd_ops[migrate_multifd_compression()];
--
2.22.3
next reply other threads:[~2023-04-25 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:05 manish.mishra [this message]
2023-04-26 10:28 ` [PATCH] multifd: Avoid busy-wait in multifd_send_pages() Juan Quintela
2023-04-26 10:39 ` manish.mishra
2023-04-26 11:05 ` Juan Quintela
2023-04-26 11:26 ` manish.mishra
2023-04-26 12:05 ` Juan Quintela
2023-04-26 12:38 ` manish.mishra
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=20230425160555.67373-1-manish.mishra@nutanix.com \
--to=manish.mishra@nutanix.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).