patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 22.11] net/mlx5: fix flow counter cache starvation
Date: Thu, 14 Mar 2024 14:12:11 +0000	[thread overview]
Message-ID: <CAMw=ZnS-72i-Oq42i0zHB5Oh96acCi0kLXBVEJiJRSR9wosWXQ@mail.gmail.com> (raw)
In-Reply-To: <20240314132905.409294-1-dsosnowski@nvidia.com>

On Thu, 14 Mar 2024 at 13:30, Dariusz Sosnowski <dsosnowski@nvidia.com> wrote:
>
> [ upstream commit d755221b77c29549be4025e547cf907ad3a0abcf ]
>
> mlx5 PMD maintains a global counter pool and per-queue counter cache,
> which are used to allocate COUNT flow action objects.
> Whenever an empty cache is accessed, it is replenished
> with a pre-defined number of counters.
>
> If number of configured counters was sufficiently small, then
> it might have happened that caches associated with some queues
> could get starved because all counters were fetched on other queues.
>
> This patch fixes that by disabling cache at runtime
> if number of configured counters is not sufficient to avoid
> such starvation.
>
> Fixes: 4d368e1da3a4 ("net/mlx5: support flow counter action for HWS")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_flow_hw.c | 10 +++--
>  drivers/net/mlx5/mlx5_hws_cnt.c | 72 ++++++++++++++++++++++++---------
>  drivers/net/mlx5/mlx5_hws_cnt.h | 26 ++++++++++++
>  3 files changed, 86 insertions(+), 22 deletions(-)

Thanks, applied

      reply	other threads:[~2024-03-14 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 13:29 Dariusz Sosnowski
2024-03-14 14:12 ` Luca Boccassi [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='CAMw=ZnS-72i-Oq42i0zHB5Oh96acCi0kLXBVEJiJRSR9wosWXQ@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=dsosnowski@nvidia.com \
    --cc=stable@dpdk.org \
    /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).