From: "Zhang, Chen" <chen.zhang@intel.com>
To: Lukas Straub <lukasstraub2@web.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Li Zhijian" <lizhijian@cn.fujitsu.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: RE: [PATCH 1/3] net/colo-compare.c: Create event_bh with the right AioContext
Date: Wed, 22 Apr 2020 08:29:39 +0000 [thread overview]
Message-ID: <5ab3bd6649a44354b087c31bb9fcd5a4@intel.com> (raw)
In-Reply-To: <b86f80bb47ac66b73b2afe80218c9913722c606a.1586370737.git.lukasstraub2@web.de>
> -----Original Message-----
> From: Lukas Straub <lukasstraub2@web.de>
> Sent: Thursday, April 9, 2020 2:34 AM
> To: qemu-devel <qemu-devel@nongnu.org>
> Cc: Zhang, Chen <chen.zhang@intel.com>; Li Zhijian
> <lizhijian@cn.fujitsu.com>; Jason Wang <jasowang@redhat.com>; Marc-
> André Lureau <marcandre.lureau@redhat.com>; Paolo Bonzini
> <pbonzini@redhat.com>
> Subject: [PATCH 1/3] net/colo-compare.c: Create event_bh with the right
> AioContext
>
> qemu_bh_new will set the bh to be executed in the main loop. This causes
> problems as colo_compare_handle_event assumes that it has exclusive
> access the queues, which are also accessed in the iothread. It also assumes
> that it runs in a different thread than the caller and takes the appropriate
> locks.
>
> Create the bh with the AioContext of the iothread to fulfill these
> assumptions.
>
Looks good for me, I assume it will increase performance. Do you have related data?
Thanks
Zhang Chen
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> net/colo-compare.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/colo-compare.c b/net/colo-compare.c index
> 10c0239f9d..1de4220fe2 100644
> --- a/net/colo-compare.c
> +++ b/net/colo-compare.c
> @@ -890,6 +890,7 @@ static void colo_compare_handle_event(void
> *opaque)
>
> static void colo_compare_iothread(CompareState *s) {
> + AioContext *ctx = iothread_get_aio_context(s->iothread);
> object_ref(OBJECT(s->iothread));
> s->worker_context = iothread_get_g_main_context(s->iothread);
>
> @@ -906,7 +907,7 @@ static void colo_compare_iothread(CompareState *s)
> }
>
> colo_compare_timer_init(s);
> - s->event_bh = qemu_bh_new(colo_compare_handle_event, s);
> + s->event_bh = aio_bh_new(ctx, colo_compare_handle_event, s);
> }
>
> static char *compare_get_pri_indev(Object *obj, Error **errp)
> --
> 2.20.1
next prev parent reply other threads:[~2020-04-22 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 18:33 [PATCH 0/3] colo-compare bugfixes Lukas Straub
2020-04-08 18:33 ` [PATCH 1/3] net/colo-compare.c: Create event_bh with the right AioContext Lukas Straub
2020-04-22 8:29 ` Zhang, Chen [this message]
2020-04-22 8:43 ` Lukas Straub
2020-04-22 9:03 ` Zhang, Chen
2020-04-22 9:40 ` Lukas Straub
2020-04-23 7:29 ` Zhang, Chen
2020-04-24 4:36 ` Derek Su
2020-04-27 3:09 ` Zhang, Chen
2020-04-08 18:33 ` [PATCH 2/3] chardev/char.c: Use qemu_co_sleep_ns if in coroutine Lukas Straub
2020-04-08 19:10 ` Marc-André Lureau
2020-04-22 8:31 ` Zhang, Chen
2020-04-08 18:33 ` [PATCH 3/3] net/colo-compare.c: Fix deadlock Lukas Straub
2020-04-22 8:40 ` Zhang, Chen
2020-04-23 14:03 ` Lukas Straub
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=5ab3bd6649a44354b087c31bb9fcd5a4@intel.com \
--to=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=lukasstraub2@web.de \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).