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: sta...@dpdk.org
Signed-off-by: Dongdong Liu <liudongdo...@huawei.com>
---
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
