From: Michael Savisko <michaelsav@nvidia.com>
To: <dev@dpdk.org>
Cc: <michaelsav@nvidia.com>, <orika@nvidia.com>,
<viacheslavo@nvidia.com>, <asafp@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: [PATCH 09/10] net/mlx5: add send to kernel action resource holder
Date: Tue, 20 Sep 2022 17:04:21 +0300 [thread overview]
Message-ID: <20220920140422.98165-10-michaelsav@nvidia.com> (raw)
In-Reply-To: <20220920140422.98165-1-michaelsav@nvidia.com>
Add new structure mlx5_send_to_kernel_action which will hold
together allocated action resource and a reference to used table.
A new structure member of this type added to struct mlx5_dev_ctx_shared.
The member will be initialized upon first created send_to_kernel
action and will be reused for all future actions of this type.
Release of these resources will be done when all shared DR
resources are being released in mlx5_os_free_shared_dr().
Signed-off-by: Michael Savisko <michaelsav@nvidia.com>
---
drivers/net/mlx5/linux/mlx5_os.c | 11 +++++++++++
drivers/net/mlx5/mlx5.h | 6 ++++++
2 files changed, 17 insertions(+)
diff --git a/drivers/net/mlx5/linux/mlx5_os.c b/drivers/net/mlx5/linux/mlx5_os.c
index 0741028dab..840e650045 100644
--- a/drivers/net/mlx5/linux/mlx5_os.c
+++ b/drivers/net/mlx5/linux/mlx5_os.c
@@ -708,6 +708,17 @@ mlx5_os_free_shared_dr(struct mlx5_priv *priv)
mlx5_glue->destroy_flow_action(sh->pop_vlan_action);
sh->pop_vlan_action = NULL;
}
+ if (sh->send_to_kernel_action.action) {
+ void *action = sh->send_to_kernel_action.action;
+ mlx5_glue->destroy_flow_action(action);
+ sh->send_to_kernel_action.action = NULL;
+ }
+ if (sh->send_to_kernel_action.tbl) {
+ struct mlx5_flow_tbl_resource *tbl =
+ sh->send_to_kernel_action.tbl;
+ flow_dv_tbl_resource_release(sh, tbl);
+ sh->send_to_kernel_action.tbl = NULL;
+ }
#endif /* HAVE_MLX5DV_DR */
if (sh->default_miss_action)
mlx5_glue->destroy_flow_action
diff --git a/drivers/net/mlx5/mlx5.h b/drivers/net/mlx5/mlx5.h
index 8af84aef50..b93d451af6 100644
--- a/drivers/net/mlx5/mlx5.h
+++ b/drivers/net/mlx5/mlx5.h
@@ -1178,6 +1178,11 @@ struct mlx5_flex_item {
struct mlx5_flex_pattern_field map[MLX5_FLEX_ITEM_MAPPING_NUM];
};
+struct mlx5_send_to_kernel_action {
+ void *action;
+ void *tbl;
+};
+
/*
* Shared Infiniband device context for Master/Representors
* which belong to same IB device with multiple IB ports.
@@ -1229,6 +1234,7 @@ struct mlx5_dev_ctx_shared {
/* Direct Rules tables for FDB, NIC TX+RX */
void *dr_drop_action; /* Pointer to DR drop action, any domain. */
void *pop_vlan_action; /* Pointer to DR pop VLAN action. */
+ struct mlx5_send_to_kernel_action send_to_kernel_action;
struct mlx5_hlist *encaps_decaps; /* Encap/decap action hash list. */
struct mlx5_hlist *modify_cmds;
struct mlx5_hlist *tag_table;
--
2.27.0
next prev parent reply other threads:[~2022-09-20 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:04 [PATCH 00/10] net/mlx5: implement send to kernel action Michael Savisko
2022-09-20 14:04 ` [PATCH 01/10] common/mlx5: update meson build file Michael Savisko
2022-09-20 14:04 ` [PATCH 02/10] net/mlx5: disable send to kernel action in HW streering Michael Savisko
2022-09-20 14:04 ` [PATCH 03/10] common/mlx5: new glue callback for send to kernel action Michael Savisko
2022-09-20 14:04 ` [PATCH 04/10] net/mlx5: add function to create " Michael Savisko
2022-09-20 14:04 ` [PATCH 05/10] net/mlx5: introduce new mlx5 action flag Michael Savisko
2022-09-20 14:04 ` [PATCH 06/10] net/mlx5: introduce new mlx5 flow fate Michael Savisko
2022-09-20 14:04 ` [PATCH 07/10] net/mlx5: get priority to send traffic to kernel Michael Savisko
2022-09-20 14:04 ` [PATCH 08/10] net/mlx5: expose table resource release function Michael Savisko
2022-09-20 14:04 ` Michael Savisko [this message]
2022-09-20 14:04 ` [PATCH 10/10] net/mlx5: translation of rte flow send to kernel action Michael Savisko
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=20220920140422.98165-10-michaelsav@nvidia.com \
--to=michaelsav@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@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).