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 3583842D73; Fri, 30 Jun 2023 09:41:00 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9DC7342D17; Fri, 30 Jun 2023 09:40:46 +0200 (CEST) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id BD57D410FC; Fri, 30 Jun 2023 09:40:41 +0200 (CEST) Received: from kwepemi500017.china.huawei.com (unknown [172.30.72.53]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4QsnJt53MdzTm1L; Fri, 30 Jun 2023 15:39:42 +0800 (CST) Received: from localhost.localdomain (10.28.79.22) by kwepemi500017.china.huawei.com (7.221.188.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Fri, 30 Jun 2023 15:40:37 +0800 From: Dongdong Liu To: , , , CC: Subject: [PATCH 3/3] doc: fix wrong number of spaces in hns3 guide Date: Fri, 30 Jun 2023 15:37:37 +0800 Message-ID: <20230630073737.20915-4-liudongdong3@huawei.com> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20230630073737.20915-1-liudongdong3@huawei.com> References: <20230630073737.20915-1-liudongdong3@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.28.79.22] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To kwepemi500017.china.huawei.com (7.221.188.110) X-CFilter-Loop: Reflected X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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") Cc: stable@dpdk.org Signed-off-by: Dongdong Liu --- doc/guides/nics/hns3.rst | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst index 644d520b64..b9f7035300 100644 --- a/doc/guides/nics/hns3.rst +++ b/doc/guides/nics/hns3.rst @@ -130,19 +130,20 @@ Runtime Configuration -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 - ``fdir_vlan_match_mode`` (default ``strict``) -- 2.22.0