From: Wang yong <wang.yong155@zte.com.cn>
To: zhang.zhanghailiang@huawei.com, zhangchen.fnst@cn.fujitsu.com,
jasowang@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
famz@redhat.com
Cc: wang.yong155@zte.com.cn, wang.guang55@zte.com.cn,
lizhijian@cn.fujitsu.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCHv3 00/02] Replace the COLO comparing thread with IOThread
Date: Wed, 16 Aug 2017 17:14:00 +0800 [thread overview]
Message-ID: <1502874842-4191-1-git-send-email-wang.yong155@zte.com.cn> (raw)
From: Wang Yong <wang.yong155@zte.com.cn>
Note: This series is based on the patch of "qemu-iothread:
IOThread supports theGMainContext event loop".
It's a good idea to use IOThread instead of COLO comparing thread.
comparing thread can be completely replaced by IOThread, so this idea came.
This series of updates mainly include the old packet regularly check and
primary/secondary network packets compare all into the IOThread processing.
Please review,thanks.
wangyong(2):
colo-compare: Use IOThread to Check old packet regularly and
Process pactkets of the primary
colo-compare: Update the COLO document to add the IOThread
configuration
docs/colo-proxy.txt | 5 +-
net/colo-compare.c | 75 ++++++++++++++++++++++++++++--------------------------
2 file changed, 39 insertions(+), 36 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-08-16 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 9:14 Wang yong [this message]
2017-08-16 9:14 ` [Qemu-devel] [PATCHv3 01/02] colo-compare: Use IOThread to Check old packet regularly and Process pactkets of the primary Wang yong
2017-08-16 9:14 ` [Qemu-devel] [PATCHv3 02/02] colo-compare: Update the COLO document to add the IOThread configuration Wang yong
2017-08-16 9:31 ` [Qemu-devel] [PATCHv3 00/02] Replace the COLO comparing thread with IOThread no-reply
2017-08-16 9:31 ` no-reply
2017-08-16 9:42 ` no-reply
2017-08-16 10:14 ` Fam Zheng
2017-08-17 2:09 ` Zhang Chen
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=1502874842-4191-1-git-send-email-wang.yong155@zte.com.cn \
--to=wang.yong155@zte.com.cn \
--cc=famz@redhat.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wang.guang55@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).