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 8955DC001DE for ; Tue, 8 Aug 2023 06:06:39 +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 E3C7929FCD for ; Tue, 8 Aug 2023 06:06:38 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id D6A919864D1 for ; Tue, 8 Aug 2023 06:06:38 +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 C787D98403A; Tue, 8 Aug 2023 06:06:38 +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 B2CB2986460; Tue, 8 Aug 2023 06:06:35 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R771e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046049;MF=xuanzhuo@linux.alibaba.com;NM=1;PH=DS;RN=5;SR=0;TI=SMTPD_---0VpJvyzs_1691474789; Message-ID: <1691474535.0577738-7-xuanzhuo@linux.alibaba.com> Date: Tue, 8 Aug 2023 14:02:15 +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> <1691467247.671468-4-xuanzhuo@linux.alibaba.com> <1691468213.0926805-6-xuanzhuo@linux.alibaba.com> In-Reply-To: Subject: [virtio-dev] Re: RE: 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 04:34:18 +0000, Parav Pandit wrote: > > > From: Xuan Zhuo > > Sent: Tuesday, August 8, 2023 9:47 AM > > > I don't care whether swtich is introduced or not. Because we have no > > dependencies on it. > > > > My requirement is to implement ip restriction which is very important for cloud > > scenarios. > > > These restrictions are needed for PF and VFs both, so can this be implemented outside of the PF and VF in your environment? I see. The point is that we want to config by the virtio admin queue (or cvq). So we want introduce this feature to the virtio. We will expose this function to the users. We want the user uses a standard way to config the ip restrictions. Thanks. > > > I think the gap is, I don't care how it's implemented. Because for me, it can be > > supported by switch rx, tx filter or virtio-net device. I'd love to hear everyone's > > opinions. > > > One proven model is to have virtio-net device to have switch object that exposes flow filters capability, if at all this is needed in your env. > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org