On 10/21/2021 3:22 AM, Min Hu (Connor) wrote:
From: Chengchang Tang<[email protected]>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. This patch add a runtime config to set the max wait time. For the above scenes, users can adjust the waiting time to a suitable value by themselves. Fixes: 463e748964f5 ("net/hns3: support mailbox") Cc:[email protected] Signed-off-by: Chengchang Tang<[email protected]> Signed-off-by: Min Hu (Connor)<[email protected]> --- v2: * add some comment for HNS3_MBX_DEF_TIME_LIMIT_MS. * remove some check for mbx_time_limit. --- drivers/net/hns3/hns3_ethdev.c | 32 ++++++++++++++++++++++++++++++- drivers/net/hns3/hns3_ethdev.h | 3 +++ drivers/net/hns3/hns3_ethdev_vf.c | 3 ++- drivers/net/hns3/hns3_mbx.c | 8 +++++--- drivers/net/hns3/hns3_mbx.h | 1 + 5 files changed, 42 insertions(+), 5 deletions(-)
New devarg need to be documented in the 'doc/guides/nics/hns3.rst', in "Runtime Config Options" section.
