From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Li Zhijian <lizhijian@cn.fujitsu.com>,
Gui jianfeng <guijianfeng@cn.fujitsu.com>,
Jason Wang <jasowang@redhat.com>,
"eddie.dong" <eddie.dong@intel.com>,
qemu devel <qemu-devel@nongnu.org>,
Yang Hongyang <hongyang.yang@easystack.cn>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH V2 0/3] Introduce COLO-compare
Date: Thu, 31 Mar 2016 14:48:37 +0800 [thread overview]
Message-ID: <56FCC845.7090705@cn.fujitsu.com> (raw)
In-Reply-To: <20160330120544.GB7580@work-vm>
On 03/30/2016 08:05 PM, Dr. David Alan Gilbert wrote:
> * Zhang Chen (zhangchen.fnst@cn.fujitsu.com) wrote:
>> COLO-compare is a part of COLO project. It is used
>> to compare the network package to help COLO decide
>> whether to do checkpoint.
> Hi Zhang Chen,
> I've put comments on the individual patches, but some more general things:
>
> 1) Please add a coment giving the example of the command line for the primary
> and secondary use of this module - it helps make it easier to understand the patches.
Yes, have reply in
Re: [Qemu-devel] [PATCH V2 1/3] colo-compare: introduce colo compare
initlization
>
> 2) There's no tracing in here - please add some; I found when I tried to get
> COLO working I needed to use lots of tracing and debugging to understand the
> packet flow.
I will add some trace in next.
>
> 3) Add comments; e.g. for each function say which thread is using it and where
> the packets are coming from; e.g.
> called from the main thread on the primary for packets arriving over the socket
> from the secondary.
>
> There's just so many packets going in so many directions it would make it
> easier to follow.
OK~
>
> 4) A more fundamental problem is what happens if the secondary never sends anything
> on the socket, the result is you end up running until the end of the long COLO
> checkpoint without triggering a discompare - in my world I added a timeout (400ms)
> for an unmatched packet from the primary, where if no matching packet was received
> a checkpoint would be triggered.
OK,I will do this in futrue
>
> 5) I see the packet comparison is still the simple memcmpy that you had in December;
> are you planning on doing anything more complicated; you must be seing most packets
> miscompare?
Yes, this is just a compare-frame RFC, We will continue to improve it in
the future
Thanks
Zhang Chen
>
> You can see my current world at; https://github.com/orbitfp7/qemu/commits/orbit-wp4-colo-mar16
> which has my basic TCP comparison (it's only tracking incoming connections) and I know it's
> not complete either. It mostly works OK, although I've got an occasional seg
> (which makes me wonder if I need to add the conn_list_lock I see you added). I'm also
> not doing any TCP reassembly which is probably needed.
>
> Dave
>
>> v2:
>> - add jhash.h
>>
>> v1:
>> - initial patch
>>
>>
>> Zhang Chen (3):
>> colo-compare: introduce colo compare initlization
>> colo-compare: track connection and enqueue packet
>> colo-compare: introduce packet comparison thread
>>
>> include/qemu/jhash.h | 59 ++++
>> net/Makefile.objs | 1 +
>> net/colo-compare.c | 782 +++++++++++++++++++++++++++++++++++++++++++++++++++
>> vl.c | 3 +-
>> 4 files changed, 844 insertions(+), 1 deletion(-)
>> create mode 100644 include/qemu/jhash.h
>> create mode 100644 net/colo-compare.c
>>
>> --
>> 1.9.1
>>
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
>
> .
>
--
Thanks
zhangchen
prev parent reply other threads:[~2016-03-31 6:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 8:35 [Qemu-devel] [PATCH V2 0/3] Introduce COLO-compare Zhang Chen
2016-03-30 8:35 ` [Qemu-devel] [PATCH V2 1/3] colo-compare: introduce colo compare initlization Zhang Chen
2016-03-30 9:25 ` Dr. David Alan Gilbert
2016-03-31 1:41 ` Zhang Chen
2016-03-31 7:25 ` Zhang Chen
2016-03-31 9:24 ` Dr. David Alan Gilbert
2016-04-01 5:11 ` Jason Wang
2016-04-01 5:41 ` Li Zhijian
2016-04-13 2:02 ` Zhang Chen
2016-03-30 8:35 ` [Qemu-devel] [PATCH V2 2/3] colo-compare: track connection and enqueue packet Zhang Chen
2016-03-30 10:36 ` Dr. David Alan Gilbert
2016-03-31 2:09 ` Li Zhijian
2016-03-31 8:47 ` Dr. David Alan Gilbert
2016-03-31 4:06 ` Zhang Chen
2016-03-31 4:23 ` Li Zhijian
2016-03-31 4:44 ` Zhang Chen
2016-03-30 8:35 ` [Qemu-devel] [PATCH V2 3/3] colo-compare: introduce packet comparison thread Zhang Chen
2016-03-30 11:41 ` Dr. David Alan Gilbert
2016-03-31 2:17 ` Li Zhijian
2016-03-31 8:50 ` Dr. David Alan Gilbert
2016-03-31 6:00 ` Zhang Chen
2016-03-30 12:05 ` [Qemu-devel] [PATCH V2 0/3] Introduce COLO-compare Dr. David Alan Gilbert
2016-03-31 3:01 ` Li Zhijian
2016-03-31 9:43 ` Dr. David Alan Gilbert
2016-04-01 1:40 ` Li Zhijian
2016-03-31 6:48 ` Zhang Chen [this message]
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=56FCC845.7090705@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=hongyang.yang@easystack.cn \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).