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: Thu, 28 Jul 2016 09:52:29 +0800 [thread overview]
Message-ID: <a417467d-eff6-9b3a-759d-e8c623b12447@redhat.com> (raw)
In-Reply-To: <c6de5f38-d48a-3895-fe30-292d0c431176@cn.fujitsu.com>
On 2016年07月27日 15:52, Zhang Chen wrote:
>
>
> On 07/27/2016 03:05 PM, Jason Wang wrote:
>>
>>
>> On 2016年07月27日 13:49, Zhang Chen wrote:
>>>
>>>
>>> On 07/27/2016 10:50 AM, Jason Wang wrote:
>>>>
>>>>
>>>> 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?
>>>
>>> COLO-compare and filter-rewriter works normal depend on colo-frame.
>>> So, When colo-frame be merged I will send a colo-proxy unit test
>>> for all filter-mirror,filter-redirector,colo-compare,filter-rewriter.
>>
>> Sounds cool.
>>
>>>
>>>
>>>>
>>>>>
>>>>> 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?
>>>
>>> Filter-rewriter can run without COLO, but it no sense for other people.
>>> rewriter need TX tcp packet differ with RX tcp packet...
>>> In normal qemu we can't get the environment same with COLO.
>>>
>>
>> Then I suggest to add this to the colo comparing series.
>
> OK~~
> BTW, Should we make independent the "qemu-char" patch to compare series?
> This patch just add a API in qemu-char.c ....
>
> Thanks
> Zhang Chen
I think yes, and better make it patch 1.
Thanks
prev parent reply other threads:[~2016-07-28 1:52 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
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 [this message]
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=a417467d-eff6-9b3a-759d-e8c623b12447@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).