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 242C1A04DD for ; Wed, 28 Oct 2020 11:48:43 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1D1AFC9D6; Wed, 28 Oct 2020 11:48:42 +0100 (CET) Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by dpdk.org (Postfix) with ESMTP id 8BB272C2A for ; Wed, 28 Oct 2020 11:48:40 +0100 (CET) Received: by mail-wm1-f65.google.com with SMTP id d3so4292864wma.4 for ; Wed, 28 Oct 2020 03:48:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=w7I8IiXS6A5tY49UCk6I8LJt24LAyelprTQKYYq0sVc=; b=q0RjCfdVyE9C4Wx04LGEdUgXQIvkKQrJsoBVXigePIL84DfbMkCpmGroblkiHOUKMa 3/ySy4OSuV1b5DPwoGLAJGSwZUheWTidU9x8SwVUPD6AscOAYQ8Lqx3AGbjLXY414bvD LdSnf7uagfZ6Ld09n2YoBG9c0lXPW8ycuQX4657JCKlj8kxu+Qrkfe1lqDU9Loj7NaFP ydx722/cHPbJJz/xZTyZ4WMWBL39fgDGc8O8DxUkBLN3rMDueuJd4r5lK4CishHCK2lI A8G3ARlNOM8a3eB2+WkGwgbVc15kY+47XQYgRG/FyXNiPwSjmTodCSYGdCbt77SPECTL WT/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=w7I8IiXS6A5tY49UCk6I8LJt24LAyelprTQKYYq0sVc=; b=cYTEkbUplPsZzV2fXofVW9c8RgGAMjGRnL7CP47ycY63+46wxJImnlXDQoTd+GLifB l4U4xK9aeutegy6DiiX4Nfv+/Ees5GevZMV+SWe9CnSmgz7vPtHuarXjyAiMF2jAfw4q l5I/9XD+SVoDR2CBu/zHE5G1ecapos/PntqdmLWQvawZy5tPKYHbbD7S9T4VA9yeaAyh dgc6gmKS7LpZsCdMQCIOnDLiCouts5ujZVKtxV8vbEFo8vQQnYqva5vXV/U7YCdQ7QFw ofNVwXSWOiJw63HV28VDSHqv7Q41xUAZwzZEuyCgx/l7ZbHa8QAvRQeIfXazXUctKKiC s52w== X-Gm-Message-State: AOAM532iTC+26CaE5isHtc5zLjK3MY6LgqAJxsUvjy31D72R8AJ8o3Q6 R6Xecl7tiPqofLqDJ02lKkY= X-Google-Smtp-Source: ABdhPJy+pTOw4wN3GWl/bHKhvnElurPBkaearp6h4fyn8d36gx/FFZZLHY8kch8Tm/s7YE2s3sIMOg== X-Received: by 2002:a1c:2cc2:: with SMTP id s185mr7696460wms.77.1603882119279; Wed, 28 Oct 2020 03:48:39 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id v19sm5687481wmj.31.2020.10.28.03.48.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Oct 2020 03:48:38 -0700 (PDT) From: luca.boccassi@gmail.com To: Heinrich Kuhn Cc: Simon Horman , dpdk stable Date: Wed, 28 Oct 2020 10:43:27 +0000 Message-Id: <20201028104606.3504127-48-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20201028104606.3504127-1-luca.boccassi@gmail.com> References: <20201028104606.3504127-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: improve multiport PF in nfp guide' has been queued to stable release 19.11.6 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to stable release 19.11.6 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 10/30/20. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Luca Boccassi --- >From bc7135aecd639de6015c1df70fe013b477941301 Mon Sep 17 00:00:00 2001 From: Heinrich Kuhn Date: Thu, 3 Sep 2020 13:23:51 +0200 Subject: [PATCH] doc: improve multiport PF in nfp guide [ upstream commit 979f2bae0714c18899e5bbb3d472842b0ce20060 ] The Agilio CX family of smartNIC's generally have a 1:many mapping of PF to physical ports. Elaborate on this mapping in the PF multiport section of the NFP PMD documentation. Fixes: d625beafc8be ("doc: update NFP with PF support information") Signed-off-by: Heinrich Kuhn Signed-off-by: Simon Horman --- doc/guides/nics/nfp.rst | 39 ++++++++++++++++++++++++++++----------- 1 file changed, 28 insertions(+), 11 deletions(-) diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst index 5f2a0698f6..020e37d131 100644 --- a/doc/guides/nics/nfp.rst +++ b/doc/guides/nics/nfp.rst @@ -102,22 +102,39 @@ directory per firmware application. Options 1 and 2 for firmware filenames allow more than one SmartNIC, same type of SmartNIC or different ones, and to upload a different firmware to each SmartNIC. + .. Note:: + Currently the NFP PMD supports using the PF with Agilio Basic Firmware. See + https://help.netronome.com/support/solutions for more information on the + various firmwares supported by the Netronome Agilio CX smartNIC. PF multiport support -------------------- -Some NFP cards support several physical ports with just one single PCI device. -The DPDK core is designed with a 1:1 relationship between PCI devices and DPDK -ports, so NFP PMD PF support requires handling the multiport case specifically. -During NFP PF initialization, the PMD will extract the information about the -number of PF ports from the firmware and will create as many DPDK ports as -needed. - -Because the unusual relationship between a single PCI device and several DPDK -ports, there are some limitations when using more than one PF DPDK port: there -is no support for RX interrupts and it is not possible either to use those PF -ports with the device hotplug functionality. +The NFP PMD can work with up to 8 ports on the same PF device. The number of +available ports is firmware and hardware dependent, and the driver looks for a +firmware symbol during initialization to know how many can be used. +DPDK apps work with ports, and a port is usually a PF or a VF PCI device. +However, with the NFP PF multiport there is just one PF PCI device. Supporting +this particular configuration requires the PMD to create ports in a special way, +although once they are created, DPDK apps should be able to use them as normal +PCI ports. + +NFP ports belonging to same PF can be seen inside PMD initialization with a +suffix added to the PCI ID: wwww:xx:yy.z_port_n. For example, a PF with PCI ID +0000:03:00.0 and four ports is seen by the PMD code as: + + .. code-block:: console + + 0000:03:00.0_port_0 + 0000:03:00.0_port_1 + 0000:03:00.0_port_2 + 0000:03:00.0_port_3 + + .. Note:: + + There are some limitations with multiport support: RX interrupts and + device hot-plugging are not supported. PF multiprocess support ----------------------- -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-10-28 10:35:13.285745936 +0000 +++ 0048-doc-improve-multiport-PF-in-nfp-guide.patch 2020-10-28 10:35:11.512830142 +0000 @@ -1,14 +1,15 @@ -From 979f2bae0714c18899e5bbb3d472842b0ce20060 Mon Sep 17 00:00:00 2001 +From bc7135aecd639de6015c1df70fe013b477941301 Mon Sep 17 00:00:00 2001 From: Heinrich Kuhn Date: Thu, 3 Sep 2020 13:23:51 +0200 Subject: [PATCH] doc: improve multiport PF in nfp guide +[ upstream commit 979f2bae0714c18899e5bbb3d472842b0ce20060 ] + The Agilio CX family of smartNIC's generally have a 1:many mapping of PF to physical ports. Elaborate on this mapping in the PF multiport section of the NFP PMD documentation. Fixes: d625beafc8be ("doc: update NFP with PF support information") -Cc: stable@dpdk.org Signed-off-by: Heinrich Kuhn Signed-off-by: Simon Horman