From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 3EC0D1DBA for ; Mon, 30 Apr 2018 16:07:44 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id t11so13438477wmt.0 for ; Mon, 30 Apr 2018 07:07:44 -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=krGFIJ79l8goycHwrUzCqY12LIj1a5iOIzY7hTPuMhE=; b=tM+ZAqQCwwbgsXqnoKxUCRvZTo0D6M818g+eOUPDYb2/lNNbxbxkWd9EasdNHfOPg9 uZi4vhQxvNYCLuHg3+2Aj96loq/Ss6JN/GhChhl9DL861h65kwBSZpfMndEN6mGFnNAl RrLV1mvH4np2kZIUUkktjNPYUAyk+7+5FMvA/VyQOBfmxa10hnJOLRx8GWYLNcCs5KX0 2upHSW8AjpuhC8+/2nvZKNEXn5S1GF+o6z9/jpSExDMnOYRj/4jGzQf9eflcwCmDZN+4 a8Pl+DaUl1C3c0a028RiB4BSXcoYH1f7eMZiVoX8v6/6zZAtCY0T7S4wWUJPBtvs0T3U sWbQ== 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=krGFIJ79l8goycHwrUzCqY12LIj1a5iOIzY7hTPuMhE=; b=jw1BvUIeMKOc4U9RKwzqZVg5MUgLIQoj35Ex2J4zgUlRkMBYmVkinfgi/6wYdjH8oR WFr5libAPvAu6kNV/aykkmcNrk6TIzPxGzRiL3qRRugcCOi8vAf8ZjJm2/N1/FHnvKdJ 0tYpBh7EPicnYqb2nbkjt1STWtChzz5ujs9D+9fNgtukCll2pVFIDOAjycDyYNpw5U2p WmmreK2K2Im1ZFw2L0AIcxdsZY4NtBsIo339/7CxbU0/syvA/ZDN3/TVIVtEawX5eqAk Wl386LMPptQXaaoN33HBRYZ+T9AjQF6CC5JmY1FTP5OPo6gmlRsxR4fWvs9rhnwjvoAw p5sw== X-Gm-Message-State: ALQs6tAxcVUfGIjHsaHAPDusC6S5aU4+oHz23In0MUQcPfIuowVqw1zg mg4MQDU4lWzlsdb3fT5jyN4= X-Google-Smtp-Source: AB8JxZrGwTZoarWp8D+9EAoHlgC2Aeg+4oiKctbaCbXxyeAun/KGLbHyT3hG/tgYZwh4Rj38IHI8hA== X-Received: by 10.28.125.74 with SMTP id y71mr7313123wmc.89.1525097263912; Mon, 30 Apr 2018 07:07:43 -0700 (PDT) Received: from localhost ([2a00:23c5:be9a:5200:ce4c:82c0:d567:ecbb]) by smtp.gmail.com with ESMTPSA id 80sm14171275wml.44.2018.04.30.07.07.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 30 Apr 2018 07:07:42 -0700 (PDT) From: luca.boccassi@gmail.com To: Alejandro Lucero Cc: Marko Kovacevic , dpdk stable Date: Mon, 30 Apr 2018 15:03:28 +0100 Message-Id: <20180430140606.4615-50-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.14.2 In-Reply-To: <20180430140606.4615-1-luca.boccassi@gmail.com> References: <20180430140606.4615-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: fix NFP NIC guide grammar' has been queued to stable release 18.02.2 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: , X-List-Received-Date: Mon, 30 Apr 2018 14:07:44 -0000 Hi, FYI, your patch has been queued to stable release 18.02.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 05/02/18. So please shout if anyone has objections. Thanks. Luca Boccassi --- >>From b26469693b8d1d97eda4f1269142739ed46d829b Mon Sep 17 00:00:00 2001 From: Alejandro Lucero Date: Thu, 22 Feb 2018 12:15:53 +0000 Subject: [PATCH] doc: fix NFP NIC guide grammar [ upstream commit 0b598c9c69ec29f088b3b5e455494df6db5a2a72 ] My english is far worse than those from the marketing team. Fixes: 80bc1752f16e ("nfp: add guide") Fixes: d625beafc8be ("doc: update NFP with PF support information") Fixes: 80987c40fd28 ("config: enable nfp driver on Linux") Signed-off-by: Alejandro Lucero Acked-by: Marko Kovacevic --- doc/guides/nics/nfp.rst | 43 ++++++++++++++++++++++--------------------- 1 file changed, 22 insertions(+), 21 deletions(-) diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst index 99a3b76eb..67e574e0a 100644 --- a/doc/guides/nics/nfp.rst +++ b/doc/guides/nics/nfp.rst @@ -34,14 +34,14 @@ NFP poll mode driver library Netronome's sixth generation of flow processors pack 216 programmable cores and over 100 hardware accelerators that uniquely combine packet, flow, security and content processing in a single device that scales -up to 400 Gbps. +up to 400-Gb/s. This document explains how to use DPDK with the Netronome Poll Mode Driver (PMD) supporting Netronome's Network Flow Processor 6xxx (NFP-6xxx) and Netronome's Flow Processor 4xxx (NFP-4xxx). NFP is a SRIOV capable device and the PMD driver supports the physical -function (PF) and virtual functions (VFs). +function (PF) and the virtual functions (VFs). Dependencies ------------ @@ -49,17 +49,18 @@ Dependencies Before using the Netronome's DPDK PMD some NFP configuration, which is not related to DPDK, is required. The system requires installation of **Netronome's BSP (Board Support Package)** along -with some specific NFP firmware application. Netronome's NSP ABI +with a specific NFP firmware application. Netronome's NSP ABI version should be 0.20 or higher. If you have a NFP device you should already have the code and -documentation for doing all this configuration. Contact +documentation for this configuration. Contact **support@netronome.com** to obtain the latest available firmware. -The NFP Linux netdev kernel driver for VFs is part of vanilla kernel -since kernel version 4.5, and support for the PF since kernel version -4.11. Support for older kernels can be obtained on Github at -**https://github.com/Netronome/nfp-drv-kmods** along with build +The NFP Linux netdev kernel driver for VFs has been a part of the +vanilla kernel since kernel version 4.5, and support for the PF +since kernel version 4.11. Support for older kernels can be obtained +on Github at +**https://github.com/Netronome/nfp-drv-kmods** along with the build instructions. NFP PMD needs to be used along with UIO ``igb_uio`` or VFIO (``vfio-pci``) @@ -70,15 +71,15 @@ Building the software Netronome's PMD code is provided in the **drivers/net/nfp** directory. Although NFP PMD has Netronome´s BSP dependencies, it is possible to -compile it along with other DPDK PMDs even if no BSP was installed before. +compile it along with other DPDK PMDs even if no BSP was installed previously. Of course, a DPDK app will require such a BSP installed for using the NFP PMD, along with a specific NFP firmware application. -Default PMD configuration is at **common_linuxapp configuration** file: +Default PMD configuration is at the **common_linuxapp configuration** file: - **CONFIG_RTE_LIBRTE_NFP_PMD=y** -Once DPDK is built all the DPDK apps and examples include support for +Once the DPDK is built all the DPDK apps and examples include support for the NFP PMD. @@ -91,18 +92,18 @@ for details. Using the PF ------------ -NFP PMD has support for using the NFP PF as another DPDK port, but it does not +NFP PMD supports using the NFP PF as another DPDK port, but it does not have any functionality for controlling VFs. In fact, it is not possible to use the PMD with the VFs if the PF is being used by DPDK, that is, with the NFP PF -bound to ``igb_uio`` or ``vfio-pci`` kernel drivers. Future DPDK version will +bound to ``igb_uio`` or ``vfio-pci`` kernel drivers. Future DPDK versions will have a PMD able to work with the PF and VFs at the same time and with the PF implementing VF management along with other PF-only functionalities/offloads. -The PMD PF has extra work to do which will delay the DPDK app initialization -like checking if a firmware is already available in the device, uploading the -firmware if necessary, and configure the Link state properly when starting or -stopping a PF port. Note that firmware upload is not always necessary which is -the main delay for NFP PF PMD initialization. +The PMD PF has extra work to do which will delay the DPDK app initialization. +This additional effort could be checking if a firmware is already available in +the device, uploading the firmware if necessary or configuring the Link state +properly when starting or stopping a PF port. Note that firmware upload is not +always necessary which is the main delay for NFP PF PMD initialization. Depending on the Netronome product installed in the system, firmware files should be available under ``/lib/firmware/netronome``. DPDK PMD supporting the @@ -114,14 +115,14 @@ PF multiport support -------------------- Some NFP cards support several physical ports with just one single PCI device. -DPDK core is designed with the 1:1 relationship between PCI devices and DPDK +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 ports: there +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. @@ -136,7 +137,7 @@ System configuration get the drivers from the above Github repository and follow the instructions for building and installing it. - Virtual Functions need to be enabled before they can be used with the PMD. + VFs need to be enabled before they can be used with the PMD. Before enabling the VFs it is useful to obtain information about the current NFP PCI device detected by the system: -- 2.14.2