From: Alexander Kozyrev <akozyrev@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <matan@nvidia.com>,
<viacheslavo@nvidia.com>, <orika@nvidia.com>, <erezsh@nvidia.com>
Subject: [PATCH 0/4] net/mlx5: implement Flow update API
Date: Mon, 12 Jun 2023 23:05:48 +0300 [thread overview]
Message-ID: <20230612200552.3450964-1-akozyrev@nvidia.com> (raw)
Add the implementation for the rte_flow_async_actions_update() API.
Construct the new actions and replace them for the Flow handle.
Old resources are freed during the rte_flow_pull() invocation.
Alexander Kozyrev (1):
net/mlx5: implement Flow update API
Erez Shitrit (3):
net/mlx5/hws: use the same function to check rule
net/mlx5/hws: use union in the wqe-data struct
net/mlx5/hws: support rule update after its creation
drivers/net/mlx5/hws/mlx5dr.h | 17 +++
drivers/net/mlx5/hws/mlx5dr_rule.c | 123 +++++++++++++-----
drivers/net/mlx5/hws/mlx5dr_send.c | 2 +-
drivers/net/mlx5/mlx5.h | 1 +
drivers/net/mlx5/mlx5_flow.c | 56 +++++++++
drivers/net/mlx5/mlx5_flow.h | 13 ++
drivers/net/mlx5/mlx5_flow_hw.c | 194 ++++++++++++++++++++++++++---
7 files changed, 362 insertions(+), 44 deletions(-)
--
2.18.2
next reply other threads:[~2023-06-12 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 20:05 Alexander Kozyrev [this message]
2023-06-12 20:05 ` [PATCH 1/4] net/mlx5/hws: use the same function to check rule Alexander Kozyrev
2023-06-14 16:59 ` Ori Kam
2023-06-12 20:05 ` [PATCH 2/4] net/mlx5/hws: use union in the wqe-data struct Alexander Kozyrev
2023-06-14 17:00 ` Ori Kam
2023-06-12 20:05 ` [PATCH 3/4] net/mlx5/hws: support rule update after its creation Alexander Kozyrev
2023-06-14 17:00 ` Ori Kam
2023-06-12 20:05 ` [PATCH 4/4] net/mlx5: implement Flow update API Alexander Kozyrev
2023-06-19 15:03 ` [PATCH 0/4] " 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=20230612200552.3450964-1-akozyrev@nvidia.com \
--to=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=erezsh@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).