From: Jason Wang <jasowang@redhat.com>
To: Yong Wang <wang.yong155@zte.com.cn>,
zhang.zhanghailiang@huawei.com, zhangchen.fnst@cn.fujitsu.com
Cc: lizhijian@cn.fujitsu.com, qemu-devel@nongnu.org, wang.guang55@zte.com.cn
Subject: Re: [Qemu-devel] [PATCHv2 01/04] colo-compare: Use IOThread context timer to Check old packet regularly
Date: Wed, 7 Jun 2017 16:30:07 +0800 [thread overview]
Message-ID: <cb49290e-9dcf-6ee0-2824-f283659f87e2@redhat.com> (raw)
In-Reply-To: <1496659493-1105-2-git-send-email-wang.yong155@zte.com.cn>
On 2017年06月05日 18:44, Yong Wang wrote:
> From: Wang Yong<wang.yong155@zte.com.cn>
>
> Remove the task which check old packet in the comparing thread,
> then use IOthread context timer to handle it.
>
> Signed-off-by: Wang Yong<wang.yong155@zte.com.cn>
> Signed-off-by: Wang Guang<wang.guang55@zte.com.cn>
> ---
> net/colo-compare.c | 62 +++++++++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 50 insertions(+), 12 deletions(-)
I suggest to squash this into patch 2, since we will have 2 threads now.
Thanks
next prev parent reply other threads:[~2017-06-07 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 10:44 [Qemu-devel] [PATCHv2 00/04] Replace the COLO comparing thread with IOThread Yong Wang
2017-06-05 10:44 ` [Qemu-devel] [PATCHv2 01/04] colo-compare: Use IOThread context timer to Check old packet regularly Yong Wang
2017-06-07 8:30 ` Jason Wang [this message]
2017-06-05 10:44 ` [Qemu-devel] [PATCHv2 02/04] colo-compare: Process pactkets in the IOThread of the primary Yong Wang
2017-06-07 8:34 ` Jason Wang
2017-06-05 10:44 ` [Qemu-devel] [PATCHv2 03/04] colo-compare: Update the COLO document to add the IOThread configuration Yong Wang
2017-06-05 10:44 ` [Qemu-devel] [PATCHv2 04/04] colo-compare: Update the COLO document to fix the processing of secondary packets in the main thread Yong Wang
2017-06-07 8:37 ` Jason Wang
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=cb49290e-9dcf-6ee0-2824-f283659f87e2@redhat.com \
--to=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--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 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).