From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 410BCA00BE; Fri, 1 Nov 2019 01:24:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 932991D413; Fri, 1 Nov 2019 01:24:50 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 3FFC61D410 for ; Fri, 1 Nov 2019 01:24:49 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6462D222C2; Thu, 31 Oct 2019 20:24:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 31 Oct 2019 20:24:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=hvSEKzZ2SBvFSBnUMCD0Ykkld3wv2jdY6gJNIa9Ph5Q=; b=Jegwt3UCOF1f cgv9SSHG64DFVpP8169By/wVysr9y50T4A8JxvIYNN4bYoNqDTP2ZNBrX+0i3awb tfmqnpDnZNpqnj1OgHIzTR3eeyEfnBF/iUO7Sz2U8+6Ytdf+ohQy+YO+IbfLEf2p i6HFOVyvwJ4jAyrin6ty0ISoJsjrMKU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=hvSEKzZ2SBvFSBnUMCD0Ykkld3wv2jdY6gJNIa9Ph 5Q=; b=GfE8wdrBzot02BVp9qIusUzwjNNdO+l8oI4sUHxNcSFEnDUSyT9RvAi/T NDq30K+9pJZCRhAK4ciD0sK9Qg9DmFpCNxCjnOQguLv9u+an8MqZm5yGvGoNA78w CRrccFW9NoCg84YivszTpDF3vjSSOjGWDVH8ZMjgjRBjGilxEfQyjiAHuoktdnjT Tt5p7odkIUYzxLTshY8NRweAs/a00wuzLig+S2EW5NF8RfGKz3v1hBV0SpeAcq6R CuyyPfhG8am7bYle7vW3ncFNey7LLpCjlu77yqkAzSRX62vEbcSArWpY5qf6CEFu nXwJUq3Nv75eviw1wpl8vgFJftXOA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtiedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeelfedrvdefrddvhedurddvvdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (227.251.23.93.rev.sfr.net [93.23.251.227]) by mail.messagingengine.com (Postfix) with ESMTPA id DA461306005C; Thu, 31 Oct 2019 20:24:45 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: dev@dpdk.org, Shahaf Shuler , Stephen Hemminger , Andrew Rybchenko , Ferruh Yigit Date: Fri, 01 Nov 2019 01:24:43 +0100 Message-ID: <1727016.NX2bq4Vah3@xps> In-Reply-To: References: <4165509.5enYigmRGf@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/3] ethdev: configure SR-IOV VF from host X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 30/10/2019 10:24, Jerin Jacob: > On Wed, Oct 30, 2019 at 12:52 PM Shahaf Shuler wrote: > > Wednesday, October 30, 2019 6:09 AM, Jerin Jacob: > > > Subject: Re: [dpdk-dev] [PATCH v2 0/3] ethdev: configure SR-IOV VF from > > > host > > > > > > On Wed, Oct 30, 2019 at 12:21 AM Thomas Monjalon > > > wrote: > > > > > > > > In a virtual environment, the network controller may have to configure > > > > some SR-IOV VF parameters for security reasons. > > > > > > Just to understand, Could you explain more details/examples for security > > > reasons? > > > > > > > > > > > When the PF (host port) is driven by DPDK (OVS-DPDK case), we face two > > > > different cases: > > > > - driver is bifurcated (Mellanox case), > > > > so the VF can be configured via the kernel. > > > > - driver is on top of UIO or VFIO, so DPDK API is required, > > > > > > Not true. Both UIO and VFIO are NOT allowed to create SRIOV VF from the > > > PF device. > > > It is only allowed through igb-uio out of tree driver without iommu support. > > > > Per my understanding Thomas proposal is not to create the VFs > > from the PF device. it is to configure their network attributes > > from the PF after they have been created. > > Yes. My question is without creating the VF, How do you control them? We can create the VF via the kernel PF driver, before binding the PF to VFIO.