xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: Xen devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	eddie dong <eddie.dong@intel.com>,
	Yang Hongyang <imhy.yang@gmail.com>,
	Bian Naimeng <biannm@cn.fujitsu.com>
Subject: [PATCH V4 0/8] COLO-Proxy: Make Xen COLO use userspace colo-proxy
Date: Mon, 6 Mar 2017 10:59:18 +0800	[thread overview]
Message-ID: <1488769166-28738-1-git-send-email-zhangchen.fnst@cn.fujitsu.com> (raw)

Because of some reason, We no longer support COLO kernel proxy.
So we send this patch set to make Xen use userspace colo-proxy in qemu.

Below is a COLO userspace proxy ascii figure:

 Primary qemu                                                           Secondary qemu
+--------------------------------------------------------------+       +----------------------------------------------------------------+
| +----------------------------------------------------------+ |       |  +-----------------------------------------------------------+ |
| |                                                          | |       |  |                                                           | |
| |                        guest                             | |       |  |                        guest                              | |
| |                                                          | |       |  |                                                           | |
| +-------^--------------------------+-----------------------+ |       |  +---------------------+--------+----------------------------+ |
|         |                          |                         |       |                        ^        |                              |
|         |                          |                         |       |                        |        |                              |
|         |  +------------------------------------------------------+  |                        |        |                              |
|netfilter|  |                       |                         |    |  |   netfilter            |        |                              |
| +----------+ +----------------------------+                  |    |  |  +-----------------------------------------------------------+ |
| |       |  |                       |      |        out       |    |  |  |                     |        |  filter excute order       | |
| |       |  |          +-----------------------------+        |    |  |  |                     |        | +------------------->      | |
| |       |  |          |            |      |         |        |    |  |  |                     |        |   TCP                      | |
| | +-----+--+-+  +-----v----+ +-----v----+ |pri +----+----+sec|    |  |  | +------------+  +---+----+---v+rewriter++  +------------+ | |
| | |          |  |          | |          | |in  |         |in |    |  |  | |            |  |        |              |  |            | | |
| | |  filter  |  |  filter  | |  filter  +------>  colo   <------+ +-------->  filter   +--> adjust |   adjust     +-->   filter   | | |
| | |  mirror  |  |redirector| |redirector| |    | compare |   |  |    |  | | redirector |  | ack    |   seq        |  | redirector | | |
| | |          |  |          | |          | |    |         |   |  |    |  | |            |  |        |              |  |            | | |
| | +----^-----+  +----+-----+ +----------+ |    +---------+   |  |    |  | +------------+  +--------+--------------+  +---+--------+ | |
| |      |   tx        |   rx           rx  |                  |  |    |  |            tx                        all       |  rx      | |
| |      |             |                    |                  |  |    |  +-----------------------------------------------------------+ |
| |      |             +--------------+     |                  |  |    |                                                   |            |
| |      |   filter excute order      |     |                  |  |    |                                                   |            |
| |      |  +---------------->        |     |                  |  +--------------------------------------------------------+            |
| +-----------------------------------------+                  |       |                                                                |
|        |                            |                        |       |                                                                |
+--------------------------------------------------------------+       +----------------------------------------------------------------+
         |guest receive               | guest send
         |                            |
+--------+----------------------------v------------------------+
|                                                              |                          NOTE: filter direction is rx/tx/all
|                         tap                                  |                          rx:receive packets sent to the netdev
|                                                              |                          tx:receive packets sent by the netdev
+--------------------------------------------------------------+

You can know the detail from here:

http://wiki.qemu.org/Features/COLO
https://github.com/qemu/qemu/blob/master/docs/colo-proxy.txt

V4:
   - Because the origin 3/7 has been merged,
     remove it in this series.
   - Add new patch "COLO-Proxy: Add colo-compare notify args"
     to support qemu side patch:
     https://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg07265.html

   - Add colo_userspace_proxy macro as a separate patch.
   - Add some comments about COLO and fix some typo in patch 2/7.
   - Fix some bug and typo in patch 7/7.
   - Rebase codes on upstream Xen.

V3:
   - remove the 'RFC' tag.
   - fix some bug in patch 7/7.
   - fix codestyle.

V2:
   - Address wei's comments, use macro to reuse codes.
   - Do some work on the last patch.
   - Fix some typo.
   - Add LIBXL_HAVE_COLO_USERSPACE_PROXY macro in libxl.h.
   - Some bug fix.

V1: 
   - Initial patch


Zhang Chen (8):
  COLO-Proxy: Add remus command to open userspace proxy
  COLO-Proxy: Setup userspace colo-proxy on primary side
  COLO-Proxy: Setup userspace colo-proxy on secondary side
  COLO-Proxy: Add primary userspace colo proxy start args
  COLO-Proxy: Add secondary userspace colo-proxy start args
  COLO-Proxy: Add colo-compare notify args
  COLO-Proxy: Use socket to get checkpoint event.
  COLO-proxy: Add colo_userspace_proxy macro

 docs/man/xl.pod.1.in             |   5 ++
 tools/libxl/libxl.h              |   6 ++
 tools/libxl/libxl_colo.h         |   7 ++
 tools/libxl/libxl_colo_proxy.c   | 149 +++++++++++++++++++++++++++++++++++++++
 tools/libxl/libxl_colo_restore.c |  19 +++--
 tools/libxl/libxl_colo_save.c    |  18 ++++-
 tools/libxl/libxl_create.c       |   8 ++-
 tools/libxl/libxl_dm.c           | 138 ++++++++++++++++++++++++++++++++++++
 tools/libxl/libxl_nic.c          | 117 ++++++++++++++++++++++++++++++
 tools/libxl/libxl_types.idl      |  68 +++++++++++++++---
 tools/xl/xl.h                    |   1 +
 tools/xl/xl_cmdtable.c           |   3 +-
 tools/xl/xl_migrate.c            |  28 ++++++--
 tools/xl/xl_parse.c              |  97 +++++++++++++++++++++++++
 tools/xl/xl_vmcontrol.c          |   2 +
 15 files changed, 642 insertions(+), 24 deletions(-)

-- 
2.7.4




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-03-06  3:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  2:59 Zhang Chen [this message]
2017-03-06  2:59 ` [PATCH V4 1/8] COLO-Proxy: Add remus command to open userspace proxy Zhang Chen
2017-03-14 11:23   ` Wei Liu
2017-03-06  2:59 ` [PATCH V4 2/8] COLO-Proxy: Setup userspace colo-proxy on primary side Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-06  2:59 ` [PATCH V4 3/8] COLO-Proxy: Setup userspace colo-proxy on secondary side Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-06  2:59 ` [PATCH V4 4/8] COLO-Proxy: Add primary userspace colo proxy start args Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-06  2:59 ` [PATCH V4 5/8] COLO-Proxy: Add secondary userspace colo-proxy " Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-14 11:39     ` Wei Liu
2017-03-15  1:53       ` Zhang Chen
2017-03-06  2:59 ` [PATCH V4 6/8] COLO-Proxy: Add colo-compare notify args Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-06  2:59 ` [PATCH V4 7/8] COLO-Proxy: Use socket to get checkpoint event Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-15  2:02     ` Zhang Chen
2017-03-15 10:56       ` Wei Liu
2017-03-16  1:21         ` Zhang Chen
2017-03-06  2:59 ` [PATCH V4 8/8] COLO-proxy: Add colo_userspace_proxy macro Zhang Chen
2017-03-14 11:24   ` Wei Liu
2017-03-06 14:31 ` [PATCH V4 0/8] COLO-Proxy: Make Xen COLO use userspace colo-proxy Konrad Rzeszutek Wilk
2017-03-07  3:25   ` 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=1488769166-28738-1-git-send-email-zhangchen.fnst@cn.fujitsu.com \
    --to=zhangchen.fnst@cn.fujitsu.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=biannm@cn.fujitsu.com \
    --cc=eddie.dong@intel.com \
    --cc=imhy.yang@gmail.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).