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 1A98C42D46 for ; Sun, 25 Jun 2023 08:40:19 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1621540ED8; Sun, 25 Jun 2023 08:40:19 +0200 (CEST) Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2063.outbound.protection.outlook.com [40.107.220.63]) by mails.dpdk.org (Postfix) with ESMTP id 604F740A7F for ; Sun, 25 Jun 2023 08:40:17 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ec647tOfaboXFZ+YaYTNsRZmkxnWBiPCKrWoAq5OIAhD+JN9PGtrfJbwduWcQrFFUgOfcf3YUH946mfFyqQrv+vH2F+KJMQ0FI6oVQjTnPYDRmCSZLv+0qciuKmKyo9pAlq0U54irBOZtNIxgmE0gxb5Lo1v5Fk2h/79iN+84YJECbsVZNNH545lndctrg+n7PL4P7j2jj9mypXzZSMCOre/gFuB+Ar6OaPP/pGeecTXNITwi3XhNcrv/J34FnWm7CiAVJ7AO7j/nSxKHRF+oQ+ShO//eEoBWk7w2y+ehK2bfoKd3AQGuyRqTgKzlxvpELOSDaO/IDHXfZUA2rce7A== 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Bz7sEaNXGndFRgTL3dPtJngll3tVH1umqNdrxhXO/J0=; b=Ftb0YYzzt5wOAELGWCh1tPDiaTuBblEWMPNhto5+zhftNtfGQxWnai2VMYE6XVdWqy9Bj1YzrfEsbVzTQccEYRfpc/ZVIk+s6cWbqAfeG0NlJFHmiHcyHXT1w6DFr7HiocPLhtniAkoiYBL7Sav7/GmLlAIE5oRVRtLUN6frodrJgT4EOQCCsq8o0++xofyQkqlwmoiPKHJjpJRxYvrSs5JiaD9OpoNhUc6fc2hlVrQ9TjqgJWE6B9d830M2pkghQAL5KEF8GZvy2Ya+hhTzjpLEXAL0Ec6pZIkvs9x6sVi8Z4hej8sXQkHYZMCKGkiumosgddX+uHeU6H/Nfw/4pQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 216.228.117.161) smtp.rcpttodomain=dpdk.org smtp.mailfrom=nvidia.com; dmarc=pass (p=reject sp=reject 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=Bz7sEaNXGndFRgTL3dPtJngll3tVH1umqNdrxhXO/J0=; b=HLOMpMPjodmux6uuluARaKdMRdYuB7qyw6A6KcpXf4iPE8pGeYC6ARzcuwpa5ryRycKHzM039mUw85/9QTDpwmMdCWTFY1arEWl+fbTYFBraqjL9OSKZT2YKBxs7qu585B6P/zkScyGfq5M6oJuMvODu+VH5HJStkrRk9Js/sLdN4nU+5UTNJ9LH58jQBFxQgsJYK/BCTLzd6RrUnapob2Tis1N/mUmSFmCxVbkxxMS+mYvg1uDPDzvF/i5d7IIA8w1PcPgjUo4vhhEDptGQbLdMpSjcW/x1CN17F22HNsFzFSUVOX2GEZyuJXzYlFeRrBq2TT8GlGjVJ+iIz9jmdA== Received: from DM5PR08CA0035.namprd08.prod.outlook.com (2603:10b6:4:60::24) by IA1PR12MB6409.namprd12.prod.outlook.com (2603:10b6:208:38b::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6521.23; Sun, 25 Jun 2023 06:40:14 +0000 Received: from DM6NAM11FT112.eop-nam11.prod.protection.outlook.com (2603:10b6:4:60:cafe::8c) by DM5PR08CA0035.outlook.office365.com (2603:10b6:4:60::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6521.33 via Frontend Transport; Sun, 25 Jun 2023 06:40:14 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 216.228.117.161) smtp.mailfrom=nvidia.com; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=nvidia.com; Received-SPF: Pass (protection.outlook.com: domain of nvidia.com designates 216.228.117.161 as permitted sender) receiver=protection.outlook.com; client-ip=216.228.117.161; helo=mail.nvidia.com; pr=C Received: from mail.nvidia.com (216.228.117.161) by DM6NAM11FT112.mail.protection.outlook.com (10.13.173.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6500.47 via Frontend Transport; Sun, 25 Jun 2023 06:40:14 +0000 Received: from rnnvmail201.nvidia.com (10.129.68.8) by mail.nvidia.com (10.129.200.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.5; Sat, 24 Jun 2023 23:40:02 -0700 Received: from nvidia.com (10.126.230.35) by rnnvmail201.nvidia.com (10.129.68.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.37; Sat, 24 Jun 2023 23:40:01 -0700 From: Xueming Li To: Michael Baum CC: Ori Kam , dpdk stable Subject: patch 'doc: fix format in flow API guide' has been queued to stable release 22.11.3 Date: Sun, 25 Jun 2023 14:34:25 +0800 Message-ID: <20230625063544.11183-48-xuemingl@nvidia.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230625063544.11183-1-xuemingl@nvidia.com> References: <20230625063544.11183-1-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.126.230.35] X-ClientProxiedBy: rnnvmail202.nvidia.com (10.129.68.7) To rnnvmail201.nvidia.com (10.129.68.8) X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: DM6NAM11FT112:EE_|IA1PR12MB6409:EE_ X-MS-Office365-Filtering-Correlation-Id: 52cfaaef-b70e-4a54-f3b4-08db7547083f X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: LhM6mg61gKW9CY0zqOnLgQk123JcgGiz7TbDTtf9jjAz+rVpKweVjdNEBxy58RtZiBwz9f/WNCjiwDbCAR1m/PKaeimtmTtJYWDE25QWuyYFQiaj2lnYILPlmzrJRH6ek+Iis9uc6yvIpSgiTZSTz2YdfGBxwiDt/RdEtOa3Qlp0Pq3HLSivOC7I+MzuXI+U+srUKgc1FXOsVDTH5EfY7tzkDSTjd5G6kHuakMxQVFDbfVuOOVgSjS5C4zmcNwrLEkO2Mz/JhSyiSR2aFPn/JMVStt7ouKQ9jL67f/mmCqviSKngEEeEvAqDj5NaiUYdqiF6ynYin7v4raSh5NXHP+MKT4hmIyA24w+eVX7t2xIVagvfF57UkfOvP8ZwvaUVap+zcJT2won8JT07MElifjFDsM/zVV7UvJLwd06K/LTSuq3GaAL/CXngmzld2jiJ6SR0uvQkGkTB5L7I46JfQDIo3hwGem+7FZEzjA6ts6LDcDI+vWHWQzEcug1QYgwd7oaCc9jEKnfp1m4Hr6NM7l4vi1LJuBYbZApoGifCOoYv6WwQoSKc8NW/IPHSznjkrJpiD6KlK/JCOcV1VFltfmTu46lhP02dgPQfVcBXm/go6XK+hXrfZ3KVmGReJr+BOdTU1l4dSzJsTLRjapbo9EvKjKfpBUt6Fuaxk+irM2QB5CFKjv//rnJ93I/6+J5We1rN4aD4AJ4urwR2TqXKp8gMwyV90EO3pFNsrgAVh2HUSKAc2XOBy2KWRD4ESUkbiksfn0fkLnUeY6kQxbVe8A== X-Forefront-Antispam-Report: CIP:216.228.117.161; CTRY:US; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:mail.nvidia.com; PTR:dc6edge2.nvidia.com; CAT:NONE; SFS:(13230028)(4636009)(376002)(136003)(396003)(39860400002)(346002)(451199021)(36840700001)(46966006)(40470700004)(82310400005)(36860700001)(47076005)(966005)(478600001)(7696005)(6666004)(2616005)(37006003)(426003)(54906003)(83380400001)(336012)(53546011)(186003)(1076003)(26005)(16526019)(6286002)(2906002)(5660300002)(36756003)(6862004)(356005)(70206006)(40460700003)(41300700001)(70586007)(82740400003)(55016003)(6636002)(7636003)(4326008)(40480700001)(8936002)(8676002)(316002)(86362001); DIR:OUT; SFP:1101; X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Jun 2023 06:40:14.3031 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 52cfaaef-b70e-4a54-f3b4-08db7547083f X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=43083d15-7273-40c1-b7db-39efd9ccc17a; Ip=[216.228.117.161]; Helo=[mail.nvidia.com] X-MS-Exchange-CrossTenant-AuthSource: DM6NAM11FT112.eop-nam11.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR12MB6409 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 Hi, FYI, your patch has been queued to stable release 22.11.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 06/27/23. 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://git.dpdk.org/dpdk-stable/log/?h=22.11-staging This queued commit can be viewed at: https://git.dpdk.org/dpdk-stable/commit/?h=22.11-staging&id=bdf2131156d22ccf14856b62fac283ad86cf3af6 Thanks. Xueming Li --- >From bdf2131156d22ccf14856b62fac283ad86cf3af6 Mon Sep 17 00:00:00 2001 From: Michael Baum Date: Wed, 24 May 2023 00:31:53 +0300 Subject: [PATCH] doc: fix format in flow API guide Cc: Xueming Li [ upstream commit 5d254667810fffe59190ca208a078bcb666a2a71 ] The modify field action description inside "Generic flow API (rte_flow)" documentation, lists all operations supported for a destination field. In addition, it lists the values supported for a encapsulation level field. Before the lists, in both cases, miss a blank line causing them to look regular text lines. This patch adds the blank lines. The asynchronous operations description inside "Generic flow API (rte_flow)" documentation, adds some bullets to describe asynchronous operations behavior. Before the first bullet, miss a blank line causing it to look a regular text line. This patch adds the blank line. The RSS action description inside "Generic flow API (rte_flow)" documentation, lists the values supported for a encapsulation level field. For "2" value, it uses 3 spaces as an indentation instead of 2 after line breaking, causing the first line to be bold. This patch updates the number of spaces in the indentation. Fixes: 73b68f4c54a0 ("ethdev: introduce generic modify flow action") Fixes: 197e820c6685 ("ethdev: bring in async queue-based flow rules operations") Fixes: 18aee2861a1f ("ethdev: add encap level to RSS flow API action") Signed-off-by: Michael Baum Acked-by: Ori Kam --- doc/guides/prog_guide/rte_flow.rst | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index 40d3f5bd44..e98f1fdd52 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -1918,8 +1918,8 @@ Also, regarding packet encapsulation ``level``: level. - ``2`` and subsequent values request RSS to be performed on the specified - inner packet encapsulation level, from outermost to innermost (lower to - higher values). + inner packet encapsulation level, from outermost to innermost (lower to + higher values). Values other than ``0`` are not necessarily supported. @@ -2881,20 +2881,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it ``RTE_FLOW_FIELD_START`` is used to point to the beginning of a packet. See ``enum rte_flow_field_id`` for the list of supported fields. -``op`` selects the operation to perform on a destination field. +``op`` selects the operation to perform on a destination field: + - ``set`` copies the data from ``src`` field to ``dst`` field. - ``add`` adds together ``dst`` and ``src`` and stores the result into ``dst``. -- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst`` +- ``sub`` subtracts ``src`` from ``dst`` and stores the result into ``dst``. ``width`` defines a number of bits to use from ``src`` field. ``level`` is used to access any packet field on any encapsulation level -as well as any tag element in the tag array. -- ``0`` means the default behaviour. Depending on the packet type, it can -mean outermost, innermost or anything in between. +as well as any tag element in the tag array: + +- ``0`` means the default behaviour. Depending on the packet type, + it can mean outermost, innermost or anything in between. - ``1`` requests access to the outermost packet encapsulation level. - ``2`` and subsequent values requests access to the specified packet -encapsulation level, from outermost to innermost (lower to higher values). + encapsulation level, from outermost to innermost (lower to higher values). + For the tag array (in case of multiple tags are supported and present) ``level`` translates directly into the array index. @@ -3602,6 +3605,7 @@ Asynchronous operations ----------------------- Flow rules management can be done via special lockless flow management queues. + - Queue operations are asynchronous and not thread-safe. - Operations can thus be invoked by the app's datapath, -- 2.25.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2023-06-25 14:31:59.773420200 +0800 +++ 0047-doc-fix-format-in-flow-API-guide.patch 2023-06-25 14:31:58.365773900 +0800 @@ -1 +1 @@ -From 5d254667810fffe59190ca208a078bcb666a2a71 Mon Sep 17 00:00:00 2001 +From bdf2131156d22ccf14856b62fac283ad86cf3af6 Mon Sep 17 00:00:00 2001 @@ -4,0 +5,3 @@ +Cc: Xueming Li + +[ upstream commit 5d254667810fffe59190ca208a078bcb666a2a71 ] @@ -31 +33,0 @@ -Cc: stable@dpdk.org @@ -40 +42 @@ -index 27fa3dd304..7116c9ce23 100644 +index 40d3f5bd44..e98f1fdd52 100644 @@ -43 +45 @@ -@@ -1968,8 +1968,8 @@ Also, regarding packet encapsulation ``level``: +@@ -1918,8 +1918,8 @@ Also, regarding packet encapsulation ``level``: @@ -54 +56 @@ -@@ -3049,20 +3049,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it +@@ -2881,20 +2881,23 @@ The immediate value ``RTE_FLOW_FIELD_VALUE`` (or a pointer to it @@ -84 +86 @@ -@@ -3856,6 +3859,7 @@ Asynchronous operations +@@ -3602,6 +3605,7 @@ Asynchronous operations