From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>
Cc: "eddie . dong" <eddie.dong@intel.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [RFC PATCH V3 0/3] filter-rewriter: introduce filter-rewriter
Date: Wed, 27 Jul 2016 10:50:13 +0800 [thread overview]
Message-ID: <cc129fb6-9941-8a88-51c6-67ba9bb32b0a@redhat.com> (raw)
In-Reply-To: <c2145631-7211-d94a-e051-3f7c58e4d21f@cn.fujitsu.com>
On 2016年07月27日 10:32, Zhang Chen wrote:
> Hi~ all~~
>
> Anyone have some comments for this series?
Will have a look at this.
Btw. I wonder how this is tested, do we need a unit test for this?
>
> We need more comments to improve COLO codes.
>
>
> Thanks
>
> Zhang Chen
>
>
> On 07/05/2016 06:29 PM, Zhang Chen wrote:
>> Filter-rewriter is a part of COLO project.
>> So this patch set depend on colo-compare.
Interesting, I thought it can co-work with comparing, and the
communication were done through socket now. So I think technically the
filter itself could work without COLO?
>> It will rewrite some of secondary packet to make
>> secondary guest's connection established successfully.
>> In this module we will rewrite tcp packet's ack to the secondary
>> from primary,and rewrite tcp packet's seq to the primary from
>> secondary.
>>
>> v3:
>> - fix typo
>> - add conn->syn_flag
>> - add some comments
>> - remove conn_list_lock
>> - fix offset set bug
I think you can remove RFC in the next version so we can try to merge it
after one or several other iterations.
Thanks
>>
>> v2:
>> - add more comments about packet flows
>> - add some trace-event
>> - add seq offset ( = secondary_seq - primary_seq)
>>
>> v1:
>> - initial patch
>>
>> Zhang Chen (3):
>> filter-rewriter: introduce filter-rewriter initialization
>> filter-rewriter: track connection and parse packet
>> filter-rewriter: rewrite tcp packet to keep secondary connection
>>
>> net/Makefile.objs | 1 +
>> net/colo-base.c | 2 +
>> net/colo-base.h | 7 ++
>> net/filter-rewriter.c | 262
>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>> qemu-options.hx | 13 +++
>> trace-events | 5 +
>> vl.c | 3 +-
>> 7 files changed, 292 insertions(+), 1 deletion(-)
>> create mode 100644 net/filter-rewriter.c
>>
>
next prev parent reply other threads:[~2016-07-27 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 10:29 [Qemu-devel] [RFC PATCH V3 0/3] filter-rewriter: introduce filter-rewriter Zhang Chen
2016-07-05 10:29 ` [Qemu-devel] [RFC PATCH V3 1/3] filter-rewriter: introduce filter-rewriter initialization Zhang Chen
2016-07-27 7:02 ` Jason Wang
2016-07-27 7:45 ` Zhang Chen
2016-07-05 10:29 ` [Qemu-devel] [RFC PATCH V3 2/3] filter-rewriter: track connection and parse packet Zhang Chen
2016-07-05 10:29 ` [Qemu-devel] [RFC PATCH V3 3/3] filter-rewriter: rewrite tcp packet to keep secondary connection Zhang Chen
2016-07-27 7:03 ` Jason Wang
2016-07-27 9:05 ` Zhang Chen
2016-07-28 2:04 ` Jason Wang
2016-07-27 2:32 ` [Qemu-devel] [RFC PATCH V3 0/3] filter-rewriter: introduce filter-rewriter Zhang Chen
2016-07-27 2:50 ` Jason Wang [this message]
2016-07-27 5:49 ` Zhang Chen
2016-07-27 7:05 ` Jason Wang
2016-07-27 7:52 ` Zhang Chen
2016-07-28 1:52 ` 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=cc129fb6-9941-8a88-51c6-67ba9bb32b0a@redhat.com \
--to=jasowang@redhat.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--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).