From: Patrick Robb <probb@iol.unh.edu>
To: Maayan Kashani <mkashani@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/mlx5/hws: fix send queue drain on FW WQE destroy
Date: Mon, 28 Apr 2025 19:58:42 -0400 [thread overview]
Message-ID: <CAJvnSUDKizObzmGnnxMhCSLWFW2trgxqPuewvZjMxo39TaJVRA@mail.gmail.com> (raw)
In-Reply-To: <20250427112821.108929-1-mkashani@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Recheck-request: iol-intel-Performance
Looks like this patch was affected by an infra failure - putting in a
retest request for the CI testing system.
On Sun, Apr 27, 2025 at 7:28 AM Maayan Kashani <mkashani@nvidia.com> wrote:
> Queue sync operation was skipped on rule destroy.
> Unlike on fw wqe rule create in which both fence and notify_hw
> are set to true, on destroy fence was set to false causing
> previous queue operation to be stuck in the queue forever.
> Example:
> rule_a - HW rule, rule_b - FW WQE rule.
> Sequence:
> rule_a destroy, burst=1 (HW rule put to queue but no DB)
> rule_b destroy, burst=0 (FW WQE rule cmd but no queue sync)
> Outcome:
> rule_a is stuck forever in the queue - no completion.
>
> Fixes: 338aaf911665 ("net/mlx5/hws: add send FW match STE using gen WQE")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alex Vesker <valex@nvidia.com>
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> ---
> drivers/net/mlx5/hws/mlx5dr_send.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/hws/mlx5dr_send.c
> b/drivers/net/mlx5/hws/mlx5dr_send.c
> index e121c7f7ed5..d01fc7ef2ca 100644
> --- a/drivers/net/mlx5/hws/mlx5dr_send.c
> +++ b/drivers/net/mlx5/hws/mlx5dr_send.c
> @@ -339,7 +339,7 @@ void mlx5dr_send_stes_fw(struct mlx5dr_send_engine
> *queue,
> pdn = ctx->pd_num;
>
> /* Writing through FW can't HW fence, therefore we drain the queue
> */
> - if (send_attr->fence)
> + if (send_attr->fence || send_attr->notify_hw)
> mlx5dr_send_queue_action(ctx,
> queue_id,
>
> MLX5DR_SEND_QUEUE_ACTION_DRAIN_SYNC);
> --
> 2.21.0
>
>
[-- Attachment #2: Type: text/html, Size: 2436 bytes --]
prev parent reply other threads:[~2025-04-29 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 11:28 Maayan Kashani
2025-04-28 23:58 ` Patrick Robb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJvnSUDKizObzmGnnxMhCSLWFW2trgxqPuewvZjMxo39TaJVRA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=mkashani@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).