From: Fam Zheng <famz@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Cc: wang.yong155@zte.com.cn, pbonzini@redhat.com,
lizhijian@cn.fujitsu.com, wang.guang55@zte.com.cn,
jasowang@redhat.com, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
marcandre.lureau@gmail.com, stefanha@redhat.com,
zhang.zhanghailiang@huawei.com
Subject: Re: [Qemu-devel] [PATCHv2 02/04] colo-compare: Processpactkets in the IOThreadofthe primary
Date: Fri, 28 Jul 2017 08:25:01 +0800 [thread overview]
Message-ID: <20170728002501.GM5117@lemon.lan> (raw)
In-Reply-To: <f53aa34f-5ca0-c38e-a303-4688698a2d42@cn.fujitsu.com>
On Thu, 07/27 15:47, Zhang Chen wrote:
> CC. Fam and David.
>
> Any idea about it?
Is it possible to use g_main_context_{push,pop}_thread_default to "move" chardev
GSources to IOThread's context, then use g_main_context_query like main thread
and poll the fds in aio_poll?
Fam
>
>
> Thanks
>
> Zhang Chen
>
>
> On 07/25/2017 09:02 AM, wang.yong155@zte.com.cn wrote:
> >
> > >On 24/07/2017 12:38, wang.yong155@zte.com.cn wrote:
> >
> > >> finally use g_main_loop_run to replace aio_poll in the
> >
> > >> iothread_run function.
> >
> > >
> >
> > >That would make the performance of virtio-blk with iothreads worse,
> >
> > >unfortunately. aio_poll is much more optimized than g_main_loop_run.
> >
> > Hi Paolo,
> >
> > Any other good idea to achieve this?
> >
> >
> > Thanks
> >
> >
> > >
> >
> > >Paolo
> >
> > >
> >
> > >> After that IOThread
> >
> > >> runs the GMainContext event loop,chardev and IOThread can work
> > together.
> >
> > >>
> >
> > >> How about it? If feasible, I will try to submit
> >
> >
> >
> >
> > 原始邮件
> > *发件人:*<pbonzini@redhat.com>;
> > *收件人:*王勇10170530;<stefanha@redhat.com>;<jasowang@redhat.com>;<marcandre.lureau@gmail.com>;
> > *抄送人:*<zhang.zhanghailiang@huawei.com>;<zhangchen.fnst@cn.fujitsu.com>;<lizhijian@cn.fujitsu.com>;<qemu-devel@nongnu.org>;王广10165992;
> > *日 期 :*2017年07月24日 19:59
> > *主 题 :**Re: [PATCHv2 02/04] colo-compare: Processpactkets in the
> > IOThreadofthe primary*
> >
> >
> > On 24/07/2017 12:38, wang.yong155@zte.com.cn wrote:
> > > finally use g_main_loop_run to replace aio_poll in the
> > > iothread_run function.
> >
> > That would make the performance of virtio-blk with iothreads worse,
> > unfortunately. aio_poll is much more optimized than g_main_loop_run.
> >
> > Paolo
> >
> > > After that IOThread
> > > runs the GMainContext event loop,chardev and IOThread can work together.
> > >
> > > How about it? If feasible, I will try to submit a patch.
> >
> >
> >
>
> --
> Thanks
> Zhang Chen
>
>
>
>
next prev parent reply other threads:[~2017-07-28 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 1:02 [Qemu-devel] [PATCHv2 02/04] colo-compare: Processpactkets in the IOThreadofthe primary wang.yong155
2017-07-27 7:47 ` Zhang Chen
2017-07-28 0:25 ` Fam Zheng [this message]
2017-08-01 10:25 ` Paolo Bonzini
2017-08-01 14:52 ` Fam Zheng
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=20170728002501.GM5117@lemon.lan \
--to=famz@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wang.guang55@zte.com.cn \
--cc=wang.yong155@zte.com.cn \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhangchen.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.