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 D5B44A0A0E for ; Mon, 10 May 2021 18:25:55 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CF5044003E; Mon, 10 May 2021 18:25:55 +0200 (CEST) Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2077.outbound.protection.outlook.com [40.107.244.77]) by mails.dpdk.org (Postfix) with ESMTP id 25CF540F35 for ; Mon, 10 May 2021 18:25:54 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A++5ZdoJ8ifxof1vVJVbcWGj3c351S9BcD7oz8PqnFg/JnD2f910KT0Ie4HwOM4k7vpgcZxwN4MH3gy6dZHMB9t02O86JOHj92JEIiw7jDkAwwihsB+cH6xh7Io/0wAE4paJxEH0SLe4Pgx5r3ZkhfGGDkaKZqwvMYwJV8hWQarPV0zqb//PvOTFChKa0C9D0PgpEllzD9p0pycanUYcykGUjAL4TqG/ydSr1umvFh2AWA2GNm4jYFhj62FbytvH1PxgazZWEW5pc7uP4tuL31kWxSTTLC2Njp+ow40TgdPLRr5uvd9+MHvmL0hrxXSv0f/C7FB/4FMqJNC03ngS1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VNTB/6D/vqEP4ddseJ/As2igJS+YBjSIMXRGqhchrkc=; b=AU8Ou6M7AQlC8n+klJbo/nkLgKZqQb9N+LIsuyjhrWeyG5XqD2gIDBH8bRVpcacUQciM8xubuuhsid9OCmoEQyre2dCKFIlaSXrKdmqZY9/A1L/0CyJsifKA7FiZB1o3H4gTJ73I7SPABhMXFCcR52Ie8to05pCsXtFzPgK3p/L2WcpP5AjcOuqDyKI4lpQX9VWPQroQP54xq1WntxF5KIxDL+Zn3VLet9Wg+KVKZWpRSCQAw6/FjPCeVDJgHlJnFoKQSXw9hpKMchtCW45eTfPIoZ72B+yzPy/k+epNBgJOzO4k9oMCEq+Xn3AjRTcXZWb9DGyx8zytkMvDs/PtgA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 216.228.112.34) smtp.rcpttodomain=dpdk.org smtp.mailfrom=nvidia.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=nvidia.com; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Nvidia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VNTB/6D/vqEP4ddseJ/As2igJS+YBjSIMXRGqhchrkc=; b=tGHHKwsSQfB5fWbeMGhyvDn0Ul0XIeNKDmUPn7z7x1OzLZjF+WYq6x8LDiIIeAsTk0mX9kkQcxUTNG3L4fOw5ur3OcGtTJW1xLYEf1jlDpx2pO3qVB/t/Mv2HUMvrqhCxK2e+Vlqvl539D0wQ8pD/pWi3oO3oSIDWdVprxscvIL8KoP8BW9JBM5avBGyZkFkk87+CuLAednWbyODC/5wnbQnrtuVNIeKp5VXDpUSpT5dvvash2bjiq76wwEilmsgUu//HnnBfci16mMaCS5aVynxzq5Fxn1qppvrxMAdOh0Fwn8XCzXLhDL/tJ3BiQZ0zqTY1yYgLoXIKS3K2X1aSA== Received: from BN0PR03CA0002.namprd03.prod.outlook.com (2603:10b6:408:e6::7) by SN1PR12MB2509.namprd12.prod.outlook.com (2603:10b6:802:29::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4108.25; Mon, 10 May 2021 16:25:52 +0000 Received: from BN8NAM11FT037.eop-nam11.prod.protection.outlook.com (2603:10b6:408:e6:cafe::eb) by BN0PR03CA0002.outlook.office365.com (2603:10b6:408:e6::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4108.25 via Frontend Transport; Mon, 10 May 2021 16:25:52 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 216.228.112.34) smtp.mailfrom=nvidia.com; dpdk.org; dkim=none (message not signed) header.d=none;dpdk.org; dmarc=pass action=none header.from=nvidia.com; Received-SPF: Pass (protection.outlook.com: domain of nvidia.com designates 216.228.112.34 as permitted sender) receiver=protection.outlook.com; client-ip=216.228.112.34; helo=mail.nvidia.com; Received: from mail.nvidia.com (216.228.112.34) by BN8NAM11FT037.mail.protection.outlook.com (10.13.177.182) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.4108.25 via Frontend Transport; Mon, 10 May 2021 16:25:52 +0000 Received: from nvidia.com (172.20.145.6) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 10 May 2021 16:25:49 +0000 From: Xueming Li To: Thomas Monjalon CC: Luca Boccassi , dpdk stable Date: Tue, 11 May 2021 00:02:58 +0800 Message-ID: <20210510160258.30982-229-xuemingl@nvidia.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210510160258.30982-1-xuemingl@nvidia.com> References: <20210510160258.30982-1-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL111.nvidia.com (172.20.187.18) To HQMAIL107.nvidia.com (172.20.187.13) X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 5879bace-09e6-43da-dea2-08d913d04782 X-MS-TrafficTypeDiagnostic: SN1PR12MB2509: X-LD-Processed: 43083d15-7273-40c1-b7db-39efd9ccc17a,ExtAddr X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: V0r04Rd4rSDU607oVPxxHTCdXI0sA23m6YpyhtFk+q+1X+JzZ9OLYAVB1bbc8u7qKzt5k1H/aDoZvUaLwr4Jeeox4AaO7fScMk0hAdTrLobCoNsx6ISbGDja0uBN9SNIdyWY5MgrXp+ExifaJS8X6sj1EJhKjr79Dzx8mYfvV0azy4GHCoPn6O8xAu3Cx9nki/8op9BI1sI4+hg0u3mf/GgThwof1jlBug7By61glUP/JnViSSP0mWXaBdv4V4bm5fPId7pwkMzERZ/rTFQk8Dg/aoPrKJ2QY90BqkMsPIhcc1ITeEdwhqKVB/h81+3b2gh7ZpnOzrScma3YePNgSrVdrZAvN+MKpqIwv9u7QQkvKIBIPeEdVy0M/Sjl9GD0qcALIZiGBnGJHzp4Sw15I1e2Jfzy3zLRY8eLOiPR7ws8eZoassiX4B6lNe6jjIfT/6OsInQ+LALU7heDcIjXEzT7owHmE5/FJiZj7ZGV0gC7YvbbX75BZplW/ItRjL860CW4Sap84FOrvDLCHdgwj0HGv6VYyD8//6z5Sh6fNm1N9NDU0xMxc27vIJiG1w/KrmBluEOM5dY6NuWB8XUevYjG3aFW2t1Tx4NH5GX6kM8whxGMZBQdEIrjvua2roFCWRL4N5cr/Yr/6JSUwJsnvnYkWnJJzz6jh9wzRzuWW3ICqI3z/sGxZacS+O1QCO7Ii/v/zDglMlPgSZ9whyy7G8Fm34/ynG+JHnaWtZxD3U3b5IVQqHqWeC0QUd2KEA6knsvkmO4A7Qvt0ysdR+od1w== X-Forefront-Antispam-Report: CIP:216.228.112.34; CTRY:US; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:mail.nvidia.com; PTR:schybrid03.nvidia.com; CAT:NONE; SFS:(4636009)(396003)(39860400002)(346002)(136003)(376002)(46966006)(36840700001)(2616005)(426003)(82310400003)(82740400003)(26005)(316002)(356005)(7636003)(1076003)(4326008)(55016002)(8676002)(70586007)(36906005)(478600001)(54906003)(70206006)(966005)(16526019)(186003)(6916009)(83380400001)(8936002)(47076005)(53546011)(6666004)(36756003)(2906002)(6286002)(336012)(5660300002)(86362001)(36860700001)(7696005); DIR:OUT; SFP:1101; X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 May 2021 16:25:52.1051 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 5879bace-09e6-43da-dea2-08d913d04782 X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=43083d15-7273-40c1-b7db-39efd9ccc17a; Ip=[216.228.112.34]; Helo=[mail.nvidia.com] X-MS-Exchange-CrossTenant-AuthSource: BN8NAM11FT037.eop-nam11.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR12MB2509 Subject: [dpdk-stable] patch 'doc: fix names of UIO drivers' has been queued to stable release 20.11.2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 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 20.11.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/12/21. 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. Queued patches are on a temporary branch at: https://github.com/steevenlee/dpdk This queued commit can be viewed at: https://github.com/steevenlee/dpdk/commit/20bbce05a8fdf7592da64bd30bc8575d931c7aff Thanks. Xueming Li --- >From 20bbce05a8fdf7592da64bd30bc8575d931c7aff Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Thu, 18 Mar 2021 12:00:49 +0100 Subject: [PATCH] doc: fix names of UIO drivers Cc: Luca Boccassi [ upstream commit b7fe612ac1de393f869c9818d5503633c8e96b36 ] Fix typos in the names of kernel drivers based on UIO, and make sure the generic term for the interface is UIO in capitals. Fixes: 3a78b2f73206 ("doc: add virtio crypto PMD guide") Fixes: 3cc4d996fa75 ("doc: update VFIO usage in qat crypto guide") Fixes: 39922c470e3c ("doc: add known uio_pci_generic issue for i40e") Fixes: 86fa6c57a175 ("doc: add known igb_uio issue for i40e") Fixes: beff6d8e8e2e ("net/netvsc: add documentation") Signed-off-by: Thomas Monjalon --- doc/guides/cryptodevs/caam_jr.rst | 2 +- doc/guides/cryptodevs/qat.rst | 2 +- doc/guides/cryptodevs/virtio.rst | 2 +- doc/guides/nics/netvsc.rst | 2 +- doc/guides/nics/virtio.rst | 5 +++-- doc/guides/nics/vmxnet3.rst | 3 ++- doc/guides/rel_notes/known_issues.rst | 10 +++++----- doc/guides/sample_app_ug/vhost.rst | 2 +- 8 files changed, 15 insertions(+), 13 deletions(-) diff --git a/doc/guides/cryptodevs/caam_jr.rst b/doc/guides/cryptodevs/caam_jr.rst index 5ef33ae78e..d7b0f14234 100644 --- a/doc/guides/cryptodevs/caam_jr.rst +++ b/doc/guides/cryptodevs/caam_jr.rst @@ -24,7 +24,7 @@ accelerators. This provides significant improvement to system level performance. SEC HW accelerator above 4.x+ version are also known as CAAM. -caam_jr PMD is one of DPAA drivers which uses uio interface to interact with +caam_jr PMD is one of DPAA drivers which uses UIO interface to interact with Linux kernel for configure and destroy the device instance (ring). diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst index cf16f03503..ea5c03b8fa 100644 --- a/doc/guides/cryptodevs/qat.rst +++ b/doc/guides/cryptodevs/qat.rst @@ -562,7 +562,7 @@ Binding the available VFs to the vfio-pci driver Note: -* Please note that due to security issues, the usage of older DPDK igb-uio +* Please note that due to security issues, the usage of older DPDK igb_uio driver is not recommended. This document shows how to use the more secure vfio-pci driver. * If QAT fails to bind to vfio-pci on Linux kernel 5.9+, please see the diff --git a/doc/guides/cryptodevs/virtio.rst b/doc/guides/cryptodevs/virtio.rst index 83d8e32397..8b96446ff2 100644 --- a/doc/guides/cryptodevs/virtio.rst +++ b/doc/guides/cryptodevs/virtio.rst @@ -63,7 +63,7 @@ QEMU can then be started using the following parameters: -device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 [...] -Secondly bind the uio_generic driver for the virtio-crypto device. +Secondly bind the uio_pci_generic driver for the virtio-crypto device. For example, 0000:00:04.0 is the domain, bus, device and function number of the virtio-crypto device: diff --git a/doc/guides/nics/netvsc.rst b/doc/guides/nics/netvsc.rst index 19f9940fe6..c0e218c743 100644 --- a/doc/guides/nics/netvsc.rst +++ b/doc/guides/nics/netvsc.rst @@ -62,7 +62,7 @@ store it in a shell variable: .. _`UUID`: https://en.wikipedia.org/wiki/Universally_unique_identifier -There are several possible ways to assign the uio device driver for a device. +There are several possible ways to assign the UIO device driver for a device. The easiest way (but only on 4.18 or later) is to use the `driverctl Device Driver control utility`_ to override the normal kernel device. diff --git a/doc/guides/nics/virtio.rst b/doc/guides/nics/virtio.rst index c03c2d0fed..aabd0f1bce 100644 --- a/doc/guides/nics/virtio.rst +++ b/doc/guides/nics/virtio.rst @@ -71,7 +71,7 @@ In this release, the virtio PMD driver provides the basic functionality of packe * Virtio supports software vlan stripping and inserting. -* Virtio supports using port IO to get PCI resource when uio/igb_uio module is not available. +* Virtio supports using port IO to get PCI resource when UIO module is not available. Prerequisites ------------- @@ -103,7 +103,8 @@ Host2VM communication example insmod rte_kni.ko - Other basic DPDK preparations like hugepage enabling, uio port binding are not listed here. + Other basic DPDK preparations like hugepage enabling, + UIO port binding are not listed here. Please refer to the *DPDK Getting Started Guide* for detailed instructions. #. Launch the kni user application: diff --git a/doc/guides/nics/vmxnet3.rst b/doc/guides/nics/vmxnet3.rst index ae146f0d55..190cf91a47 100644 --- a/doc/guides/nics/vmxnet3.rst +++ b/doc/guides/nics/vmxnet3.rst @@ -119,7 +119,8 @@ This section describes an example setup for Phy-vSwitch-VM-Phy communication. .. note:: - Other instructions on preparing to use DPDK such as, hugepage enabling, uio port binding are not listed here. + Other instructions on preparing to use DPDK such as, + hugepage enabling, UIO port binding are not listed here. Please refer to *DPDK Getting Started Guide and DPDK Sample Application's User Guide* for detailed instructions. The packet reception and transmission flow path is:: diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst index ee3ed1e658..e8f9fe6023 100644 --- a/doc/guides/rel_notes/known_issues.rst +++ b/doc/guides/rel_notes/known_issues.rst @@ -419,7 +419,7 @@ Binding PCI devices to igb_uio fails on Linux kernel 3.9 when more than one devi ------------------------------------------------------------------------------------------ **Description**: - A known bug in the uio driver included in Linux kernel version 3.9 prevents more than one PCI device to be + A known bug in the UIO driver included in Linux kernel version 3.9 prevents more than one PCI device to be bound to the igb_uio driver. **Implication**: @@ -614,7 +614,7 @@ I40e VF may not receive packets in the promiscuous mode Poll Mode Driver (PMD). -uio pci generic module bind failed in X710/XL710/XXV710 +uio_pci_generic module bind failed in X710/XL710/XXV710 ------------------------------------------------------- **Description**: @@ -671,7 +671,7 @@ virtio tx_burst() function cannot do TSO on shared packets Poll Mode Driver (PMD). -igb uio legacy mode can not be used in X710/XL710/XXV710 +igb_uio legacy mode can not be used in X710/XL710/XXV710 -------------------------------------------------------- **Description**: @@ -752,7 +752,7 @@ Netvsc driver and application restart handshake sequence with the host. **Resolution/Workaround**: - Either reboot the guest or remove and reinsert the hv_uio_generic module. + Either reboot the guest or remove and reinsert the uio_hv_generic module. **Affected Environment/Platform**: Linux Hyper-V. @@ -816,7 +816,7 @@ Kernel crash when hot-unplug igb_uio device while DPDK application is running **Reason**: When device is hot-unplugged, igb_uio driver will be removed which will destroy UIO resources. - Later trying to access any uio resource will cause kernel crash. + Later trying to access any UIO resource will cause kernel crash. **Resolution/Workaround**: If using DPDK for PCI HW hot-unplug, prefer to bind device with VFIO instead of IGB_UIO. diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst index 15aaff2493..d00693b293 100644 --- a/doc/guides/sample_app_ug/vhost.rst +++ b/doc/guides/sample_app_ug/vhost.rst @@ -72,7 +72,7 @@ Run testpmd inside guest ~~~~~~~~~~~~~~~~~~~~~~~~ Make sure you have DPDK built inside the guest. Also make sure the -corresponding virtio-net PCI device is bond to a uio driver, which +corresponding virtio-net PCI device is bond to a UIO driver, which could be done by: .. code-block:: console -- 2.25.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2021-05-10 23:59:32.486753900 +0800 +++ 0230-doc-fix-names-of-UIO-drivers.patch 2021-05-10 23:59:26.710000000 +0800 @@ -1 +1 @@ -From b7fe612ac1de393f869c9818d5503633c8e96b36 Mon Sep 17 00:00:00 2001 +From 20bbce05a8fdf7592da64bd30bc8575d931c7aff Mon Sep 17 00:00:00 2001 @@ -4,0 +5,3 @@ +Cc: Luca Boccassi + +[ upstream commit b7fe612ac1de393f869c9818d5503633c8e96b36 ] @@ -14 +16,0 @@ -Cc: stable@dpdk.org @@ -42 +44 @@ -index 224b22b3f7..96f5ab6afe 100644 +index cf16f03503..ea5c03b8fa 100644 @@ -81 +83 @@ -index 02e74a6e77..ac07d4d1e5 100644 +index c03c2d0fed..aabd0f1bce 100644 @@ -118 +120 @@ -index 43323e1a43..beea877bad 100644 +index ee3ed1e658..e8f9fe6023 100644 @@ -167 +169 @@ -index 09b1b6c57d..9afde9c7f5 100644 +index 15aaff2493..d00693b293 100644