All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: Wang yong <wang.yong155@zte.com.cn>,
	pbonzini@redhat.com, stefanha@redhat.com, famz@redhat.com,
	jasowang@redhat.com, zhang.zhanghailiang@huawei.com
Cc: zhangchen.fnst@cn.fujitsu.com, wang.guang55@zte.com.cn,
	lizhijian@cn.fujitsu.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv5 03/03] colo-compare: Update the COLO document to add the IOThread configuration
Date: Thu, 7 Sep 2017 11:23:26 +0800	[thread overview]
Message-ID: <bdbcecf3-af7a-3cae-7e8b-ded4eadbc604@cn.fujitsu.com> (raw)
In-Reply-To: <1503991359-3353-4-git-send-email-wang.yong155@zte.com.cn>



On 08/29/2017 03:22 PM, Wang yong wrote:
> From: Wang Yong <wang.yong155@zte.com.cn>
>
> Update colo-proxy.txt,add IOThread configuration.
> Later we have to configure IOThread,if not COLO can not work.
>
> Signed-off-by: Wang Yong <wang.yong155@zte.com.cn>
> Signed-off-by: Wang Guang <wang.guang55@zte.com.cn>

Reviewed-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>

> ---
>   docs/colo-proxy.txt | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/docs/colo-proxy.txt b/docs/colo-proxy.txt
> index c4941de..ce3f783 100644
> --- a/docs/colo-proxy.txt
> +++ b/docs/colo-proxy.txt
> @@ -170,10 +170,11 @@ Primary(ip:3.3.3.3):
>   -chardev socket,id=compare0-0,host=3.3.3.3,port=9001
>   -chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
>   -chardev socket,id=compare_out0,host=3.3.3.3,port=9005
> +-object iothread,id=iothread1
>   -object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
>   -object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
>   -object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
> --object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
> +-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0,iothread=iothread1
>   
>   Secondary(ip:3.3.3.8):
>   -netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown

-- 
Thanks
Zhang Chen

  reply	other threads:[~2017-09-07  3:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  7:22 [Qemu-devel] [PATCHv5 00/03] Replace the COLO comparing thread with IOThread Wang yong
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 01/03] qemu-iothread: IOThread supports the GMainContext event loop Wang yong
2017-08-31  2:18   ` Fam Zheng
2017-08-31  6:45     ` Fam Zheng
2017-08-31 10:13   ` Stefan Hajnoczi
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 02/03] colo-compare: Use IOThread to Check old packet regularly and Process pactkets of the primary Wang yong
2017-09-07  3:22   ` Zhang Chen
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 03/03] colo-compare: Update the COLO document to add the IOThread configuration Wang yong
2017-09-07  3:23   ` Zhang Chen [this message]
2017-09-08  1:32 ` [Qemu-devel] [PATCHv5 00/03] Replace the COLO comparing thread with IOThread 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=bdbcecf3-af7a-3cae-7e8b-ded4eadbc604@cn.fujitsu.com \
    --to=zhangchen.fnst@cn.fujitsu.com \
    --cc=famz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wang.guang55@zte.com.cn \
    --cc=wang.yong155@zte.com.cn \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.