From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0A5DCC04A6A for ; Tue, 8 Aug 2023 04:07:06 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 3FC862AC8D for ; Tue, 8 Aug 2023 04:07:05 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 2F60A986499 for ; Tue, 8 Aug 2023 04:07:05 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 2023C983EB3; Tue, 8 Aug 2023 04:07:05 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 0AB63986460; Tue, 8 Aug 2023 04:07:04 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R311e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018045192;MF=xuanzhuo@linux.alibaba.com;NM=1;PH=DS;RN=5;SR=0;TI=SMTPD_---0VpJbx7v_1691467618; Message-ID: <1691467247.671468-4-xuanzhuo@linux.alibaba.com> Date: Tue, 8 Aug 2023 12:00:47 +0800 From: Xuan Zhuo To: Parav Pandit Cc: "virtio-dev@lists.oasis-open.org" , "virtio-comment@lists.oasis-open.org" , "Michael S. Tsirkin" , Jason Wang References: <20230803083150.46745-1-xuanzhuo@linux.alibaba.com> <20230803054333-mutt-send-email-mst@kernel.org> <1691059929.235804-1-xuanzhuo@linux.alibaba.com> <1691060652.3764465-2-xuanzhuo@linux.alibaba.com> <1691061508.9066079-5-xuanzhuo@linux.alibaba.com> <1691062204.2378864-7-xuanzhuo@linux.alibaba.com> <1691062877.0013635-8-xuanzhuo@linux.alibaba.com> <1691129914.3255427-1-xuanzhuo@linux.alibaba.com> <1691132049.7182267-2-xuanzhuo@linux.alibaba.com> <1691135097.4908528-3-xuanzhuo@linux.alibaba.com> <20230804053958-mutt-send-email-mst@kernel.org> <1691388171.3192031-1-xuanzhuo@linux.alibaba.com> <1691462188.324996-1-xuanzhuo@linux.alibaba.com> In-Reply-To: Subject: [virtio-dev] Re: RE: RE: RE: RE: RE: [virtio-comment] RE: RE: RE: RE: [RFC] virtio-net: support access and control the member devices On Tue, 8 Aug 2023 03:16:44 +0000, Parav Pandit wrote: > > > > From: Jason Wang > > Sent: Tuesday, August 8, 2023 8:39 AM > > > > > Yes, but even for TX, would it be better to filter the IP as early as possible in the > > TX path other than depend on the switch to do that? > > The idea is to introduce filters on the new virtio switch object for tx and rx both. Filters for tx? Are there other use cases? > A virtio switch object can be part of a existing virtio device or a new virtio device type in itself. > > Xuan, > As we discussed, since the owner device packets also needs to be filtered, potentially outside of the owner device itself, > > Do you see the need to introduce virtio switch object now, or can it wait? For virtio switch, I am ok. But for me, I just have this requirement that needs the switch. So if we do this in the device, then that is not need for me. Now, you think we should introduce the rx/tx filter to the virtio switch. @Jason @Michael how do you think? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org