From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: Jason Wang <jasowang@redhat.com>, qemu devel <qemu-devel@nongnu.org>
Cc: zhangchen.fnst@cn.fujitsu.com,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V3 0/4] Optimize COLO-compare performance
Date: Mon, 21 Aug 2017 13:17:39 +0800 [thread overview]
Message-ID: <b6b722c0-76c8-f79b-694d-4f1370ef475f@cn.fujitsu.com> (raw)
In-Reply-To: <f00fdc9a-6f9a-bae2-78a0-9d1124ca9640@redhat.com>
On 08/21/2017 11:55 AM, Jason Wang wrote:
>
>
> On 2017年08月21日 09:45, Zhang Chen wrote:
>> Hi~~ All~
>>
>> No one review this series for a long time.
>>
>> Ping...
>>
>>
>
> Looks ok to me. But I don't like patch 1 since it adds more TODO
> especially for a non-exist function colo_notify_checkpoint().
>
> I tend to have it after colo_notify_checkpoint() is implemented or
> merged.
>
I got your point, I will send the V4 without patch1.
Thanks
Zhang Chen
> Thanks
>
>
>
>
--
Thanks
Zhang Chen
prev parent reply other threads:[~2017-08-21 5:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 7:29 [Qemu-devel] [PATCH V3 0/4] Optimize COLO-compare performance Zhang Chen
2017-07-19 7:29 ` [Qemu-devel] [PATCH V3 1/4] net/colo-compare.c: Add checkpoint min period to optimize performance Zhang Chen
2017-07-19 7:29 ` [Qemu-devel] [PATCH V3 2/4] net/colo-compare.c: Optimize unpredictable tcp options comparison Zhang Chen
2017-07-19 7:29 ` [Qemu-devel] [PATCH V3 3/4] net/colo-compare.c: Adjust net queue pop order for performance Zhang Chen
2017-07-19 7:29 ` [Qemu-devel] [PATCH V3 4/4] net/colo-compare.c: Fix comments and scheme Zhang Chen
2017-07-19 10:20 ` [Qemu-devel] [PATCH V3 0/4] Optimize COLO-compare performance no-reply
2017-08-21 1:45 ` Zhang Chen
2017-08-21 3:55 ` Jason Wang
2017-08-21 5:17 ` 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=b6b722c0-76c8-f79b-694d-4f1370ef475f@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=dgilbert@redhat.com \
--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).