qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: qemu-devel@nongnu.org, jasowang@redhat.com
Cc: zhangchen.fnst@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Juan Quintela <quintela@redhat.com>,
	Amit Shah <amit.shah@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	eddie.dong@intel.com, Xu Quan <xuquan8@huawei.com>
Subject: [Qemu-devel] [PATCH 0/3] colo-compare: Preparing work for combining with COLO frame
Date: Tue, 24 Jan 2017 22:05:45 +0800	[thread overview]
Message-ID: <1485266748-15340-1-git-send-email-zhang.zhanghailiang@huawei.com> (raw)

Hi,

This series is some preparing works for integrating colo-compare into COLO
frame.

It is based on patch '[PATCH] colo-compare: sort TCP packet queue by sequence number'
http://patchwork.ozlabs.org/patch/718955/ 

Please review and any commits are welcomed.

Cc: Juan Quintela <quintela@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>
Cc: Dr. David Alan Gilbert (git) <dgilbert@redhat.com>
Cc: eddie.dong@intel.com
Cc: Xu Quan <xuquan8@huawei.com>


Zhang Chen (1):
  colo-compare: add API to flush all queued packets while do checkpoint

zhanghailiang (2):
  colo-compare: reconstruct the mutex lock usage
  colo-compare: use notifier to notify inconsistent packets comparing

 net/colo-compare.c | 105 +++++++++++++++++++++++++++++++++++++++++++++++------
 net/colo-compare.h |  22 +++++++++++
 net/colo.c         |   2 +
 net/colo.h         |   2 +
 4 files changed, 119 insertions(+), 12 deletions(-)
 create mode 100644 net/colo-compare.h

-- 
1.8.3.1

             reply	other threads:[~2017-01-24 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 14:05 zhanghailiang [this message]
2017-01-24 14:05 ` [Qemu-devel] [PATCH 1/3] colo-compare: reconstruct the mutex lock usage zhanghailiang
2017-02-03  3:47   ` Jason Wang
2017-02-06  8:13     ` Hailiang Zhang
2017-02-06  8:30       ` Zhang Chen
2017-02-06  9:35       ` Jason Wang
2017-02-06 11:11         ` Hailiang Zhang
2017-02-06 12:53           ` Jason Wang
2017-02-07  7:54             ` Hailiang Zhang
2017-02-07  7:57               ` Jason Wang
2017-02-07  8:19                 ` Hailiang Zhang
2017-02-07  9:21                   ` Jason Wang
2017-02-07  9:30                     ` Hailiang Zhang
2017-02-14  2:32                     ` Hailiang Zhang
2017-02-14  4:08                       ` Jason Wang
2017-02-14  7:33                         ` Hailiang Zhang
2017-02-15  3:16                           ` Jason Wang
2017-01-24 14:05 ` [Qemu-devel] [PATCH 2/3] colo-compare: add API to flush all queued packets while do checkpoint zhanghailiang
2017-01-24 14:05 ` [Qemu-devel] [PATCH 3/3] colo-compare: use notifier to notify inconsistent packets comparing zhanghailiang
2017-02-03  4:50   ` Jason Wang
2017-02-06  8:44     ` Hailiang Zhang
2017-02-06  9:35       ` Jason Wang

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=1485266748-15340-1-git-send-email-zhang.zhanghailiang@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=xuquan8@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).