From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: <getelson@nvidia.com>, <mkashani@nvidia.com>,
<rasland@nvidia.com>, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: [PATCH] net/mlx5: fix pattern template size validation
Date: Wed, 6 Mar 2024 09:38:56 +0200 [thread overview]
Message-ID: <20240306073856.950136-1-getelson@nvidia.com> (raw)
PMD running in HWS FDB mode can be configured to steer group 0 to FW.
In that case PMD activates legacy DV pattern processing.
There are control flows that require HWS pattern processing
in group 0.
Pattern template validation tried to create a matcher both in group 0
and HWS group.
As the result, during group 0 validation HWS tuned pattern was
processed as DV.
The patch removed pattern validation for group 0.
Fixes: f3aadd103358 ("net/mlx5: improve pattern template validation")
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
drivers/net/mlx5/mlx5_flow_hw.c | 49 +++++++++++++++++++--------------
1 file changed, 29 insertions(+), 20 deletions(-)
diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c
index 4216433c6e..b37348c972 100644
--- a/drivers/net/mlx5/mlx5_flow_hw.c
+++ b/drivers/net/mlx5/mlx5_flow_hw.c
@@ -7668,48 +7668,57 @@ flow_hw_pattern_has_sq_match(const struct rte_flow_item *items)
return false;
}
+/*
+ * Verify that the tested flow patterns fits STE size limit in HWS group.
+ *
+ *
+ * Return values:
+ * 0 : Tested patterns fit STE size limit
+ * -EINVAL : Invalid parameters detected
+ * -E2BIG : Tested patterns exceed STE size limit
+ */
static int
pattern_template_validate(struct rte_eth_dev *dev,
struct rte_flow_pattern_template *pt[], uint32_t pt_num)
{
- uint32_t group = 0;
+ struct rte_flow_error error;
struct mlx5_flow_template_table_cfg tbl_cfg = {
- .attr = (struct rte_flow_template_table_attr) {
+ .attr = {
.nb_flows = 64,
.insertion_type = RTE_FLOW_TABLE_INSERTION_TYPE_PATTERN,
.hash_func = RTE_FLOW_TABLE_HASH_FUNC_DEFAULT,
.flow_attr = {
+ .group = 1,
.ingress = pt[0]->attr.ingress,
.egress = pt[0]->attr.egress,
.transfer = pt[0]->attr.transfer
}
- },
- .external = true
+ }
};
struct mlx5_priv *priv = dev->data->dev_private;
struct rte_flow_actions_template *action_template;
+ struct rte_flow_template_table *tmpl_tbl;
+ int ret;
- if (pt[0]->attr.ingress) {
+ if (pt[0]->attr.ingress)
action_template = priv->action_template_drop[MLX5DR_TABLE_TYPE_NIC_RX];
- } else if (pt[0]->attr.egress) {
+ else if (pt[0]->attr.egress)
action_template = priv->action_template_drop[MLX5DR_TABLE_TYPE_NIC_TX];
- } else if (pt[0]->attr.transfer) {
+ else if (pt[0]->attr.transfer)
action_template = priv->action_template_drop[MLX5DR_TABLE_TYPE_FDB];
+ else
+ return -EINVAL;
+ if (pt[0]->item_flags & MLX5_FLOW_ITEM_COMPARE)
+ tbl_cfg.attr.nb_flows = 1;
+ tmpl_tbl = flow_hw_table_create(dev, &tbl_cfg, pt, pt_num,
+ &action_template, 1, NULL);
+ if (tmpl_tbl) {
+ ret = 0;
+ flow_hw_table_destroy(dev, tmpl_tbl, &error);
} else {
- rte_errno = EINVAL;
- return rte_errno;
+ ret = rte_errno == E2BIG ? -E2BIG : 0;
}
- do {
- struct rte_flow_template_table *tmpl_tbl;
-
- tbl_cfg.attr.flow_attr.group = group;
- tmpl_tbl = flow_hw_table_create(dev, &tbl_cfg, pt, pt_num,
- &action_template, 1, NULL);
- if (!tmpl_tbl)
- return rte_errno;
- flow_hw_table_destroy(dev, tmpl_tbl, NULL);
- } while (++group <= 1);
- return 0;
+ return ret;
}
/**
--
2.39.2
next reply other threads:[~2024-03-06 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:38 Gregory Etelson [this message]
2024-03-13 7:44 ` Raslan Darawsheh
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=20240306073856.950136-1-getelson@nvidia.com \
--to=getelson@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@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).