From: Chenghai Huang <huangchenghai2@huawei.com> During asynchronous performance testing, it is common for devices to become busy. Simply retrying the operation is sufficient. Printing too many busy messages can affect user experience. Signed-off-by: Chenghai Huang <huangchenghai2@huawei.com> Signed-off-by: Zongyu Wu <wuzongyu1@huawei.com> --- wd_comp.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/wd_comp.c b/wd_comp.c index 435f5a8..5e62462 100644 --- a/wd_comp.c +++ b/wd_comp.c @@ -913,7 +913,9 @@ int wd_do_comp_async(handle_t h_sess, struct wd_comp_req *req) ret = wd_alg_driver_send(wd_comp_setting.driver, ctx->ctx, msg); if (unlikely(ret < 0)) { - WD_ERR("wd comp send error, ret = %d!\n", ret); + if (ret != -WD_EBUSY) + WD_ERR("wd comp send error, ret = %d!\n", ret); + goto fail_with_msg; } -- 2.33.0