From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>
Cc: Li Zhijian <lizhijian@cn.fujitsu.com>,
bian naimeng <biannm@cn.fujitsu.com>,
"eddie . dong" <eddie.dong@intel.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH V3 0/3] COLO-compare: Optimize the code and fix some bug
Date: Mon, 6 Mar 2017 13:21:36 +0800 [thread overview]
Message-ID: <058c8c25-ec73-542d-a3d5-c40f38ac0b33@redhat.com> (raw)
In-Reply-To: <1488448458-4976-1-git-send-email-zhangchen.fnst@cn.fujitsu.com>
On 2017年03月02日 17:54, Zhang Chen wrote:
> This series we will Optimize the code and fix some bug.
> Patch1: Rename colo_packet_compare() and remove duplicate check in compare icmp.
> Patch2: Optimize compare_common and increase compare performance.
> Patch3: Fix debug info always print bug.
>
> Zhang Chen (3):
> COLO-compare: Rename compare function and remove duplicate codes
> COLO-compare: Optimize compare_common and compare_tcp
> COLO-compare: Fix icmp and udp compare different packet always dump
> bug
>
> net/colo-compare.c | 74 ++++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 49 insertions(+), 25 deletions(-)
>
Applied, thanks.
prev parent reply other threads:[~2017-03-06 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 9:54 [Qemu-devel] [PATCH V3 0/3] COLO-compare: Optimize the code and fix some bug Zhang Chen
2017-03-02 9:54 ` [Qemu-devel] [PATCH V3 1/3] COLO-compare: Rename compare function and remove duplicate codes Zhang Chen
2017-03-02 9:54 ` [Qemu-devel] [PATCH V3 2/3] COLO-compare: Optimize compare_common and compare_tcp Zhang Chen
2017-03-02 9:54 ` [Qemu-devel] [PATCH V3 3/3] COLO-compare: Fix icmp and udp compare different packet always dump bug Zhang Chen
2017-03-06 5:21 ` Jason Wang [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=058c8c25-ec73-542d-a3d5-c40f38ac0b33@redhat.com \
--to=jasowang@redhat.com \
--cc=biannm@cn.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--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).