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 F2DBA4301F for ; Thu, 10 Aug 2023 02:01:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC4F340DD8; Thu, 10 Aug 2023 02:01:13 +0200 (CEST) Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2078.outbound.protection.outlook.com [40.107.237.78]) by mails.dpdk.org (Postfix) with ESMTP id 91893406B6 for ; Thu, 10 Aug 2023 02:01:12 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Gt/Ui2ZzyY+aylHDeazjKIZR51Tb3NkDcS6DiMwlWibweWoWFv7aGzqZLSI2ywaJkAU6kAqC4QKcO5vzoe7TGtzHVBEgX35yNG/xhRAxjbXRpt7aBFnhyXfCEEIql4lWoDt8wwpvsNjn4+VR/h+HidZiejy4mVqvKfIwOama55mrKRqP7pyfLvWIb6fK3DWcFBR4hfsLtPkGo9dnAaQFY/UhQix0SNnqsZXALCLSM5uSL+cDyziKM8K6fXjW2wnclHGpXay4qKfTJ7rplO6zG2M07XH+bN+hCjlBG53t/5Fb2a6QcQoNJhg5ZAtEj5aoYQfcFCZMkRKSmWHcGVQ33A== 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=wYx+/Bajr36S7WLrLW+oxbHVGaiVLyfLoK3gJSTGKoo=; b=H94YVrC/kLwbB5XFp1c9gol9Jsr0/B1NNvGRtEx7RCqV4MemY8QWNTS9h0GqGSHhTOdxqoResqKZ9/2MF6UqkAP6olgBIKR/4zBseXG10w+h6Vkpnf5AUinptpnRZOlAOkVKA3auS/fVPj0+XZXejVLqqLqryPnGvvKKDN95R66fiYB2mS+LiK+fG9npha68wKQUgoqO+tu9qiL0EsyVj7Jrc0G72m9LGFzeOcDcOriy0f5kv53KPPySezsgHaR/NkfvH6C5ShBhFV1E7aL2W1ASvcAzsv7IIRgDk4iT5OoAcO+hSsfeKXyg5nQGyY8VayLqT2pR/RN4QFFzVTvoSQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 216.228.117.160) smtp.rcpttodomain=huawei.com 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=wYx+/Bajr36S7WLrLW+oxbHVGaiVLyfLoK3gJSTGKoo=; b=rgwPsJRQ8Ypohm7wjNGbXtoFeih+k05bwf5VPArMfMACutMKyvxWCy6XRd4tYOkVeftf08SNGnv+ZuI/PaWhrWeAv/K+5m3KNbWTTpqtLZXT7gNIZ+92B1Scr60tNyNAlkBNtAYetbVNMaVfO9SziIZZ9ZxdC4NGTFv86xIACVdFlL07vyq8F0ixMRNjiB0jcQplW3MWymTUU73zPfnkz9QwEd990vdZowoPfPX0ZEymFtlofGNbi+d37FH0TUPj3bC5ILpzghNHhxn48q2bjj5zxgu6+v9pLLIIl2LPWKFzgb5Ytf/LCJAJlwxFxI3oBT3RqYt8ufTyRhxKNV60Hg== Received: from CY5PR19CA0130.namprd19.prod.outlook.com (2603:10b6:930:64::17) by CO6PR12MB5394.namprd12.prod.outlook.com (2603:10b6:5:35f::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6652.28; Thu, 10 Aug 2023 00:01:11 +0000 Received: from CY4PEPF0000E9CF.namprd03.prod.outlook.com (2603:10b6:930:64:cafe::27) by CY5PR19CA0130.outlook.office365.com (2603:10b6:930:64::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6652.28 via Frontend Transport; Thu, 10 Aug 2023 00:01:10 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 216.228.117.160) 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.160 as permitted sender) receiver=protection.outlook.com; client-ip=216.228.117.160; helo=mail.nvidia.com; pr=C Received: from mail.nvidia.com (216.228.117.160) by CY4PEPF0000E9CF.mail.protection.outlook.com (10.167.241.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6652.19 via Frontend Transport; Thu, 10 Aug 2023 00:01:09 +0000 Received: from rnnvmail201.nvidia.com (10.129.68.8) by mail.nvidia.com (10.129.200.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.5; Wed, 9 Aug 2023 17:00:57 -0700 Received: from nvidia.com (10.126.230.37) 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; Wed, 9 Aug 2023 17:00:55 -0700 From: Xueming Li To: Dongdong Liu CC: dpdk stable Subject: patch 'doc: fix number of leading spaces in hns3 guide' has been queued to stable release 22.11.3 Date: Thu, 10 Aug 2023 07:58:43 +0800 Message-ID: <20230809235947.1187-11-xuemingl@nvidia.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230809235947.1187-1-xuemingl@nvidia.com> References: <20230625063544.11183-1-xuemingl@nvidia.com> <20230809235947.1187-1-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.126.230.37] 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: CY4PEPF0000E9CF:EE_|CO6PR12MB5394:EE_ X-MS-Office365-Filtering-Correlation-Id: e9b432f0-d232-4512-f396-08db9934e72a X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: OvkligfdNHVAvyBlJtYHJ9GWR/GNdjHRAJoLNas2m6F9jcmIG9V0nsQuxXpFKAphuCc9bv3/KTkMXpMbv6m7w8DYF0sDalcceUNqLtPpk8+jcuYzx23kWU68uuFcIggzkO3y0yOramfhvDEtiNEsDT7k0rVJ53leB2ChFKYS7N0ZSAEbWr1Ms5WrSWALezu8X30FZjK+uxn31/F0kROqmAsB+5DqWBZ0Wk9fbFELnxIQ/IHqSfPc85dbXKeZ2R9v11AzpK5AaRYEa4kp7Pfse0YlQVjj1vqGhK7WfNpvodtn64+9andiSCVIedwTK+4gfWHtbYOsXbWRAbhhjpKX3RbUv5CQanh8R8FqUqO+IwEGe654sK0y0OPnfh4H43KJQOUW8HOwxSijej8WaK0VqLlqWaiW6I5EhhwBLDgPfLEHt7FagFZ73jePmx3kZMV7SPIUTjzOJH+Us9kx6aT5dGu7yzY85U5hdUzdfgp7xZqVNfVvKvdgaMPrCPGHNb2dXJL1Fw/wNzABo5nznLtW2AKlK42jsrJHAjyAgtXpHF8lHva4xRZyVhfXDOA37VsC+KXdtfpmK34wPoHKfkShvnv42JQB+dGW3U2EPADG2+5/uUl3D4mGolHsKV+PYXkao3ymeoZsu7p22XNM/CXYpllfvv2/7386tBbc4E+r4GS0ZyLbUhSmmxIEDiZREsX5Q8ywypbYhxbwVBSFIBLE8Nq6/mJT9BvVhhPIMcReaOkxu8EFN1tFD8QrgsRKkw8HoqsrsMYIjjJbceU/UqLI5Q== X-Forefront-Antispam-Report: CIP:216.228.117.160; CTRY:US; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:mail.nvidia.com; PTR:dc6edge1.nvidia.com; CAT:NONE; SFS:(13230028)(4636009)(346002)(136003)(396003)(376002)(39860400002)(82310400008)(186006)(1800799006)(451199021)(40470700004)(36840700001)(46966006)(426003)(356005)(478600001)(82740400003)(7636003)(16526019)(6286002)(36860700001)(2616005)(336012)(83380400001)(47076005)(55016003)(40460700003)(6916009)(966005)(1076003)(26005)(53546011)(40480700001)(70586007)(41300700001)(8936002)(316002)(2906002)(4326008)(6666004)(7696005)(36756003)(8676002)(70206006)(86362001)(5660300002); DIR:OUT; SFP:1101; X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Aug 2023 00:01:09.7195 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: e9b432f0-d232-4512-f396-08db9934e72a 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.160]; Helo=[mail.nvidia.com] X-MS-Exchange-CrossTenant-AuthSource: CY4PEPF0000E9CF.namprd03.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO6PR12MB5394 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 08/11/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=7a44cac46c71c87928c34f401641f74788d7019e Thanks. Xueming Li --- >From 7a44cac46c71c87928c34f401641f74788d7019e Mon Sep 17 00:00:00 2001 From: Dongdong Liu Date: Fri, 30 Jun 2023 15:37:37 +0800 Subject: [PATCH] doc: fix number of leading spaces in hns3 guide Cc: Xueming Li [ upstream commit 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb ] The current description of 'mbx_time_limit_ms' has three spaces at the beginning. Use two spaces to keep the same style with other places and add a blank line after '::'. Fixes: 2fc3e696a7f1 ("net/hns3: add runtime config for mailbox limit time") Signed-off-by: Dongdong Liu --- doc/guides/nics/hns3.rst | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst index 8a6998fd65..6fbd4320ef 100644 --- a/doc/guides/nics/hns3.rst +++ b/doc/guides/nics/hns3.rst @@ -82,7 +82,7 @@ Runtime Config Options For example:: - -a 0000:7d:00.0,rx_func_hint=simple + -a 0000:7d:00.0,rx_func_hint=simple - ``tx_func_hint`` (default ``none``) @@ -103,7 +103,7 @@ Runtime Config Options For example:: - -a 0000:7d:00.0,tx_func_hint=common + -a 0000:7d:00.0,tx_func_hint=common - ``dev_caps_mask`` (default ``0``) @@ -116,22 +116,24 @@ Runtime Config Options For example:: - -a 0000:7d:00.0,dev_caps_mask=0xF + -a 0000:7d:00.0,dev_caps_mask=0xF - ``mbx_time_limit_ms`` (default ``500``) - Used to define the mailbox time limit by user. - Current, the max waiting time for MBX response is 500ms, but in - some scenarios, it is not enough. Since it depends on the response - of the kernel mode driver, and its response time is related to the - scheduling of the system. In this special scenario, most of the - cores are isolated, and only a few cores are used for system - scheduling. When a large number of services are started, the - scheduling of the system will be very busy, and the reply of the - mbx message will time out, which will cause our PMD initialization - to fail. So provide access to set mailbox time limit for user. - - For example:: - -a 0000:7d:00.0,mbx_time_limit_ms=600 + + Used to define the mailbox time limit by user. + Current, the max waiting time for MBX response is 500ms, but in + some scenarios, it is not enough. Since it depends on the response + of the kernel mode driver, and its response time is related to the + scheduling of the system. In this special scenario, most of the + cores are isolated, and only a few cores are used for system + scheduling. When a large number of services are started, the + scheduling of the system will be very busy, and the reply of the + mbx message will time out, which will cause our PMD initialization + to fail. So provide access to set mailbox time limit for user. + + For example:: + + -a 0000:7d:00.0,mbx_time_limit_ms=600 Link status event Pre-conditions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.25.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2023-08-09 21:51:19.825621700 +0800 +++ 0064-doc-fix-number-of-leading-spaces-in-hns3-guide.patch 2023-08-09 21:51:18.204352000 +0800 @@ -1 +1 @@ -From 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb Mon Sep 17 00:00:00 2001 +From 7a44cac46c71c87928c34f401641f74788d7019e Mon Sep 17 00:00:00 2001 @@ -4,0 +5,3 @@ +Cc: Xueming Li + +[ upstream commit 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb ] @@ -11 +13,0 @@ -Cc: stable@dpdk.org @@ -19 +21 @@ -index 11cbc992e7..ee774639d3 100644 +index 8a6998fd65..6fbd4320ef 100644 @@ -22 +24 @@ -@@ -93,7 +93,7 @@ Runtime Configuration +@@ -82,7 +82,7 @@ Runtime Config Options @@ -31 +33 @@ -@@ -114,7 +114,7 @@ Runtime Configuration +@@ -103,7 +103,7 @@ Runtime Config Options @@ -40 +42 @@ -@@ -127,22 +127,24 @@ Runtime Configuration +@@ -116,22 +116,24 @@ Runtime Config Options @@ -77,2 +79,2 @@ - - ``fdir_vlan_match_mode`` (default ``strict``) - + Link status event Pre-conditions + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~