From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 12672A00C5; Mon, 31 Oct 2022 16:53:40 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B27C340223; Mon, 31 Oct 2022 16:53:39 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 84DAC40151 for <dev@dpdk.org>; Mon, 31 Oct 2022 16:53:38 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 36F7A5C0180; Mon, 31 Oct 2022 11:53:36 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 31 Oct 2022 11:53:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1667231616; x= 1667318016; bh=4bB70/NYod0NdqBCL7XpX7z9Fc6zG79Vb53epp+o558=; b=s ET415mDPRmepESsZAp3h+qVQ/OPnIpYkoHuYMUXVHrKADPwppChKePUGXJj9TBTI j725aStoM+ULR1wKqLkwJaoUIIokg9AZTJpBCSrhhPqVCZMEFUAOoQXJ8qsBoLJu PIvqFzx8IJW5ClMAg7k9Noi2oIr7fksXNFnT099fdWZSgzNj3cAirqJaBQOa1z73 l4Zjf15HnIwUm4zU7imhPI1k14GART5ujB6BO2RPCxJSh0EEus1WzbSzTI6vBr4u UyXrQALfr7AabxXGf3InzPJTawcs6OB3thx3ZMCRGAQWKhQKAcBlXraMGRJI8un3 qSKOnLXA35HyHO1c9lmMA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1667231616; x= 1667318016; bh=4bB70/NYod0NdqBCL7XpX7z9Fc6zG79Vb53epp+o558=; b=D u83JlOWEOeACayvzAGALhrShLQVa1mx4OTHBs6fjVnZtoAzzsSbJ9/hpYK+3O9rC 8NepbQWWx9X7u9ECVxRt8Q28ljdTtACLtN8Ck3WrgSJZx3+D/V6UB6SMIIXXw6U7 Xn6DlUPexmSmIs5kVBvTNTdYYONGqTjocIEd9cSkiNBCTgPptKLRknFXtJoc7KmC fRBYxqUbdwm84waJUuqRalcMiHEfAaqlXlsFGg8bKFkJmLg03m1YELp/zMqPk5MP FEzD4OKJRyAymPanzOWhDch7JK+ObFCBSH5nR42/USN4+PQONHR2yTOgmOwhk7Rc B1Ha8AjtnyRC3cdG2NH8A== X-ME-Sender: <xms:f-9fY-5gf248f25a9ETQuGqk4V0gwfXAJYYRv6U3d-MayM1A37RPvw> <xme:f-9fY341sIQMA5-aYLN1BVgL38aR7wlLPXauu-RlGsDHjEoj9q9NXUct0-10KChEG O8qoTbfEZUZuxj1sA> X-ME-Received: <xmr:f-9fY9dSnlpneP6ipuGQqagWotdulBde1opd6oQpYfPXoWqbAlxhkgj8Hwc_-ZuxBoaOBiDW159Mt7qVLIDi> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrudefgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: <xmx:f-9fY7Lb7ejXMOxiMBepbS5Nnxmc0oW3O40IHEeoqIBWsJNAUfem2w> <xmx:f-9fYyI7BAEOekD0vq3tENq00aPjSRxnUveh8SaLrp1xdJfOQEzSrg> <xmx:f-9fY8xVLLwiEth8v7QD1NzYrrSDgfWGmxB_-zvQRxFaUu7uKP8lUw> <xmx:gO9fYx-f85_C9dLexRBQbnzTwlKGZ81zOoGbkugOmw98lcn0Rp_wLg> Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 31 Oct 2022 11:53:34 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: "Chautru, Nicolas" <nicolas.chautru@intel.com> Cc: dev@dpdk.org, "gakhil@marvell.com" <gakhil@marvell.com>, "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>, "trix@redhat.com" <trix@redhat.com>, "Richardson, Bruce" <bruce.richardson@intel.com>, "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>, "david.marchand@redhat.com" <david.marchand@redhat.com>, "stephen@networkplumber.org" <stephen@networkplumber.org>, "Vargas, Hernan" <hernan.vargas@intel.com> Subject: Re: [PATCH v12 04/16] baseband/acc: introduce PMD for ACC200 Date: Mon, 31 Oct 2022 16:53:33 +0100 Message-ID: <2968027.687JKscXgg@thomas> In-Reply-To: <BY5PR11MB445175E8BA7FDD587E03F2CCF8379@BY5PR11MB4451.namprd11.prod.outlook.com> References: <20221012175930.7560-1-nicolas.chautru@intel.com> <3141057.vfdyTQepKt@thomas> <BY5PR11MB445175E8BA7FDD587E03F2CCF8379@BY5PR11MB4451.namprd11.prod.outlook.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org 31/10/2022 16:43, Chautru, Nicolas: > From: Thomas Monjalon <thomas@monjalon.net> > > 12/10/2022 19:59, Nicolas Chautru: > > > +Bind PF UIO driver(s) > > > +~~~~~~~~~~~~~~~~~~~~~ > > > + > > > +Install the DPDK igb_uio driver, bind it with the PF PCI device ID > > > +and use ``lspci`` to confirm the PF device is under use by ``igb_uio`` DPDK > > UIO driver. > > > > igb_uio is not recommended. > > Please focus on VFIO first. > > > > > +The igb_uio driver may be bound to the PF PCI device using one of two > > > +methods for ACC200: > > > + > > > + > > > +1. PCI functions (physical or virtual, depending on the use case) can > > > +be bound to the UIO driver by repeating this command for every function. > > > + > > > +.. code-block:: console > > > + > > > + cd <dpdk-top-level-directory> > > > + insmod ./build/kmod/igb_uio.ko > > > + echo "8086 57c0" > /sys/bus/pci/drivers/igb_uio/new_id > > > + lspci -vd8086:57c0 > > > + > > > + > > > +2. Another way to bind PF with DPDK UIO driver is by using the > > > +``dpdk-devbind.py`` tool > > > + > > > +.. code-block:: console > > > + > > > + cd <dpdk-top-level-directory> > > > + ./usertools/dpdk-devbind.py -b igb_uio 0000:f7:00.0 > > > + > > > +where the PCI device ID (example: 0000:f7:00.0) is obtained using > > > +lspci -vd8086:57c0 > > > > This binding is not specific to the driver. > > It would be better to refer to the Linux guide instead of duplicating it again > > and again. > > > > > +In a similar way the PF may be bound with vfio-pci as any PCIe device. > > > > You could mention igb_uio here. > > Is there any advantage in using igb_uio? > > > > Igb_uio is arguably easier to use to new user tend to start with it or specific ecosystem. This is typically the entry point (no iommu, no flr below the bonnet, no vfio token...) hence good to have a bit of handholding with a couple of lines capturing how to easily run a few tests. I don't believe this is too redundant to have these few lines compared to the help in bring to the user not having to double guess their steps. > More generally there are a number of module drivers combinations that are supported based on different deployments. We don't document in too much details for the details since that is not too ACC specific and there is more documentation no pf_bb_config repo for using the PMD from the VF.. > > Basically Thomas let us know more explicitly what you are suggesting as documentation update. You just want more emphasis on vfio-pci flow (which is fair, some of it documented on pf_bb_config including the vfio token passing but we can reproduce here as well) or something else? There are 2 things to change: 1/ igb_uio is going to be deprecated, so we must emphasize on VFIO 2/ for doc maintenance, it is better to have common steps described in one place. If needed, you can change the common doc and refer to it.