From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNa5J-0004yU-Ek for qemu-devel@nongnu.org; Mon, 25 Jan 2016 00:53:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNa5G-0000el-1h for qemu-devel@nongnu.org; Mon, 25 Jan 2016 00:53:05 -0500 Received: from szxga01-in.huawei.com ([58.251.152.64]:40653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNa5F-0000eB-8t for qemu-devel@nongnu.org; Mon, 25 Jan 2016 00:53:01 -0500 References: <1453451811-11860-1-git-send-email-zhang.zhanghailiang@huawei.com> <20160122100756.GD14825@redhat.com> <56A59734.8080004@redhat.com> From: Hailiang Zhang Message-ID: <56A5B782.5030703@huawei.com> Date: Mon, 25 Jan 2016 13:49:54 +0800 MIME-Version: 1.0 In-Reply-To: <56A59734.8080004@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC 0/7] Netfilter: Add each netdev a default filter List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jason Wang , "Daniel P. Berrange" Cc: hongyang.yang@easystack.cn, peter.huangpeng@huawei.com, zhangchen.fnst@cn.fujitsu.com, qemu-devel@nongnu.org On 2016/1/25 11:32, Jason Wang wrote: > > > On 01/22/2016 06:07 PM, Daniel P. Berrange wrote: >> On Fri, Jan 22, 2016 at 04:36:44PM +0800, zhanghailiang wrote: >>> This series is a prerequisite for COLO, here we add each netdev >>> a default buffer filter, it is disabled by default, and has >>> no side effect for delivering packets in net layer. >> Why can't whatever is launching QEMU just setup filters explicitly >> if they want to use COLO ? I'm not seeing an obvious compelling >> reason to add this by default and then add extra code to deal >> with special casing its behaviour. > > Two things here I think. The first is the management role for COLO, > maybe it's time to discuss it now. And if management can do this, it's Yes, better to confirm it as early as possible, the later COLO based on proxy also have such problem. > ok for not implementing default filter now. Second is the default filter > itself, I still think it's not bad to have it for the future, and with > the ability to specify, change or disable the default filter. This could > simplify management and testing. > > Back to this series, it mixes several things (bugs fixings, new 'status' > filed, default filter implementation, and a special handling for > filter-buffer). Better split them. > OK, i will do that, thanks. > Thanks >> >>> Besides, patch 1 fixes the ouput information of 'info network' command >>> for filter. >>> >>> zhanghailiang (7): >>> net/filter: Fix the output information for command 'info network' >>> net/filter: Add a 'status' property for filter object >>> net/filter: Skip the disabled filter when delivering packets >>> net/filter: Introduce a helper to add a filter to the netdev >>> filter-buffer: Accept zero interval >>> net/filter: Add a default filter to each netdev >>> net/filter: prevent the default filter to be deleted >>> >>> include/net/filter.h | 25 +++++++- >>> net/dump.c | 2 - >>> net/filter-buffer.c | 10 ---- >>> net/filter.c | 163 +++++++++++++++++++++++++++++++++++++++++++++------ >>> net/net.c | 27 ++++++++- >>> 5 files changed, 194 insertions(+), 33 deletions(-) >> Regards, >> Daniel > > > . >