From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: <getelson@nvidia.com>, <mkashani@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: [PATCH v3 0/2] net/mlx5: update pattern validations
Date: Mon, 12 Feb 2024 15:59:09 +0200 [thread overview]
Message-ID: <20240212135911.529237-1-getelson@nvidia.com> (raw)
In-Reply-To: <20240202150617.328603-1-getelson@nvidia.com>
PMD updates `rte_errno` if pattern template validation failed:
E2BIG - pattern too big for PMD
ENOTSUP - pattern not supported by PMD
ENOMEM - PMD allocation failure
Gregory Etelson (2):
net/mlx5/hws: definer, update pattern validations
net/mlx5: improve pattern template validation
drivers/net/mlx5/hws/mlx5dr_definer.c | 4 +-
drivers/net/mlx5/mlx5.h | 1 +
drivers/net/mlx5/mlx5_flow_hw.c | 121 ++++++++++++++++++++++++++
3 files changed, 125 insertions(+), 1 deletion(-)
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
--
2.39.2
next prev parent reply other threads:[~2024-02-12 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:06 [PATCH 0/2] net/mlx5: update pattern validations Gregory Etelson
2024-02-02 15:06 ` [PATCH 1/2] net/mlx5/hws: definer, " Gregory Etelson
2024-02-06 12:27 ` Dariusz Sosnowski
2024-02-12 12:32 ` [PATCH v2 0/2] net/mlx5: " Gregory Etelson
2024-02-12 12:32 ` [PATCH v2 1/2] net/mlx5/hws: definer, " Gregory Etelson
2024-02-12 12:32 ` [PATCH v2 2/2] net/mlx5: improve pattern template validation Gregory Etelson
2024-02-02 15:06 ` [PATCH " Gregory Etelson
2024-02-06 12:26 ` Dariusz Sosnowski
2024-02-12 13:59 ` Gregory Etelson [this message]
2024-02-12 13:59 ` [PATCH v3 1/2] net/mlx5/hws: definer, update pattern validations Gregory Etelson
2024-02-12 13:59 ` [PATCH v3 2/2] net/mlx5: improve pattern template validation Gregory Etelson
2024-02-26 12:07 ` [PATCH v3 0/2] net/mlx5: update pattern validations 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=20240212135911.529237-1-getelson@nvidia.com \
--to=getelson@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.