From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: qemu devel <qemu-devel@nongnu.org>, Jason Wang <jasowang@redhat.com>
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH V4 0/3] Optimize COLO-compare performance
Date: Mon, 21 Aug 2017 16:55:16 +0800 [thread overview]
Message-ID: <1503305719-2512-1-git-send-email-zhangchen.fnst@cn.fujitsu.com> (raw)
In this serise, we do a lot of job to optimize COLO net performance.
Mainly focus on TCP protocol.
V4:
- Remove the old patch1.
V3:
- Rebase on upstream.
- Remove origin p2.
- Move the "checkpoint_time_ms" to CompareState,
in order to aviod multi colo-compare instance conflict.
- Add "TODO comments" for reset s->checkpoint_time_ms.
- Add a new patch fix comments and scheme.
V2:
- Rename p2's subject.
Zhang Chen (3):
net/colo-compare.c: Optimize unpredictable tcp options comparison
net/colo-compare.c: Adjust net queue pop order for performance
net/colo-compare.c: Fix comments and scheme
net/colo-compare.c | 62 +++++++++++++++++++++++++++++++++++-------------------
1 file changed, 40 insertions(+), 22 deletions(-)
--
2.7.4
next reply other threads:[~2017-08-21 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 8:55 Zhang Chen [this message]
2017-08-21 8:55 ` [Qemu-devel] [PATCH V4 1/3] net/colo-compare.c: Optimize unpredictable tcp options comparison Zhang Chen
2017-09-01 9:35 ` Dou Liyang
2017-09-01 16:02 ` Zhang Chen
2017-09-04 1:52 ` Dou Liyang
2017-08-21 8:55 ` [Qemu-devel] [PATCH V4 2/3] net/colo-compare.c: Adjust net queue pop order for performance Zhang Chen
2017-08-21 8:55 ` [Qemu-devel] [PATCH V4 3/3] net/colo-compare.c: Fix comments and scheme Zhang Chen
2017-08-22 7:16 ` [Qemu-devel] [PATCH V4 0/3] Optimize COLO-compare performance no-reply
2017-08-29 9:01 ` Jason Wang
2017-08-29 10:45 ` Fam Zheng
2017-08-30 1:47 ` Jason Wang
2017-08-29 5:34 ` 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=1503305719-2512-1-git-send-email-zhangchen.fnst@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
/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).