From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3FA99A00C2; Sun, 30 Oct 2022 17:03:03 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AE6B740693; Sun, 30 Oct 2022 17:03:02 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id AB07440151 for ; Sun, 30 Oct 2022 17:03:01 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 4665E5C008D; Sun, 30 Oct 2022 12:03:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 30 Oct 2022 12:03:00 -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=1667145780; x= 1667232180; bh=8wO38wLB+fZfSrC81BEpvWI5SwIeynCnOA9Q1A0weZg=; b=y 6TsTm2tvCin0RAwqLknW90gWJXu+EJwYLSHTOIU7wQPWKE8+lwDtwW6aLcKyocpG S5zLXSpSpMIUZzG/dBlDxd7Py9lEjWvRkrrfBri//yo7BOLuCmcd52d3Zdu4EP5r V6+Q4FqJPHt/5wk+txxAfefajO3bOaMF1aOeahd+f/bBL8M7zYNCMBoCNJY9UQ0u XjPh1BMdxo+3dWHqL+jTPx0k70G/mgFqNU3rZQuacW+zOUNRpe6CdMX53w283oFl HOkzkyPHiMKBSd677/7fu+hqnATBaN+VmWL/PwMd3ABrwq18qwiAzMzu+BFHa8b9 dbwXQZJQIfy19yfBTWzeg== 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=1667145780; x= 1667232180; bh=8wO38wLB+fZfSrC81BEpvWI5SwIeynCnOA9Q1A0weZg=; b=P ivDkK+8bZ5i+VAsnbzcTR36/e+0aFnYGzKzA0OOpJAUU4MNaLHia/JdJUn00uqJs Bmyju5p+riu2zePkjmWGkRsaKnOb4WotpaxhlpypkCJVobmIyjQ7mzTHjmEQjXYY nNIbrz2U/gVNNMsOoSApU9pkUCTOweLl3qw7jeDqk0NiK+GGIX0O9KwFhrMcqOYq 9VuPR1el1uv2NLj96ewIdobCXXKMw+PTdF9ynh8zM9+ykPd5Xv0+y+skFCHNEOfK 2nT7832klyTLhP339Wf/KOuk4k6Yno0MYhVYTFQVMIwyHB/CPtWWiQuGf+rUaTeb rX9J97fM71A9gHw/eu+pQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedruddtgdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 30 Oct 2022 12:02:58 -0400 (EDT) From: Thomas Monjalon To: Nicolas Chautru Cc: dev@dpdk.org, gakhil@marvell.com, maxime.coquelin@redhat.com, trix@redhat.com, bruce.richardson@intel.com, hemant.agrawal@nxp.com, david.marchand@redhat.com, stephen@networkplumber.org, hernan.vargas@intel.com Subject: Re: [PATCH v12 04/16] baseband/acc: introduce PMD for ACC200 Date: Sun, 30 Oct 2022 17:02:57 +0100 Message-ID: <3141057.vfdyTQepKt@thomas> In-Reply-To: <20221012175930.7560-5-nicolas.chautru@intel.com> References: <20221012175930.7560-1-nicolas.chautru@intel.com> <20221012175930.7560-5-nicolas.chautru@intel.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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 > + 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 > + ./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?