From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: Raslan Darawsheh <rasland@nvidia.com>, <dev@dpdk.org>
Subject: [PATCH 0/2] net/mlx5: fix counter query loop getting stuck
Date: Wed, 30 Oct 2024 17:30:44 +0100 [thread overview]
Message-ID: <20241030163046.495982-1-dsosnowski@nvidia.com> (raw)
Main content of this patchset is "net/mlx5: fix counter query loop getting stuck" patch.
The preceding patch is required, because the fix for counter query loop
triggered the dangling pointer compilation error in GCC 14.2.1 in an unrelated
part of the code. To be specific, the following part caused the error:
```
@@ -3978,7 +3982,7 @@ flow_hw_async_flow_create(struct rte_eth_dev *dev,
&table->ats[action_template_index],
table->its[pattern_template_index]->item_flags,
flow->table, actions,
- rule_acts, queue, error))
+ rule_acts, queue, &sub_error))
goto error;
rule_items = flow_hw_get_rule_items(dev, table, items,
pattern_template_index, &priv->hw_q[queue].pp);
```
Dariusz Sosnowski (2):
net/mlx5: fix dangling pointer to params
net/mlx5: fix counter query loop getting stuck
doc/guides/nics/mlx5.rst | 71 +++++++++++++++++++++++++++++++++
drivers/net/mlx5/mlx5.h | 28 +++++++++++++
drivers/net/mlx5/mlx5_flow.h | 25 ------------
drivers/net/mlx5/mlx5_flow_hw.c | 26 +++++++-----
drivers/net/mlx5/mlx5_hws_cnt.c | 46 ++++++++++++---------
5 files changed, 141 insertions(+), 55 deletions(-)
--
2.39.5
next reply other threads:[~2024-10-30 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 16:30 Dariusz Sosnowski [this message]
2024-10-30 16:30 ` [PATCH 1/2] net/mlx5: fix dangling pointer to params Dariusz Sosnowski
2024-10-30 16:30 ` [PATCH 2/2] net/mlx5: fix counter query loop getting stuck Dariusz Sosnowski
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=20241030163046.495982-1-dsosnowski@nvidia.com \
--to=dsosnowski@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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).