From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Vlad Buslov <vladbu@nvidia.com>,
Dmytro Linkin <dlinkin@nvidia.com>, Roi Dayan <roid@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: [net-next 03/17] net/mlx5e: Always set attr mdev pointer
Date: Thu, 4 Feb 2021 22:40:37 -0800 [thread overview]
Message-ID: <20210205064051.89592-4-saeed@kernel.org> (raw)
In-Reply-To: <20210205064051.89592-1-saeed@kernel.org>
From: Vlad Buslov <vladbu@nvidia.com>
Eswitch offloads extensions in following patches in the series require
attr->esw_attr->in_mdev pointer to always be set. This is already the case
for all code paths except mlx5_tc_ct_entry_add_rule() function. Fix the
function to assign mdev pointer with priv->mdev value.
Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
Signed-off-by: Dmytro Linkin <dlinkin@nvidia.com>
Reviewed-by: Roi Dayan <roid@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
---
drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c
index 40aaa105b2fc..3fb75dcdc68d 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c
@@ -711,6 +711,8 @@ mlx5_tc_ct_entry_add_rule(struct mlx5_tc_ct_priv *ct_priv,
attr->outer_match_level = MLX5_MATCH_L4;
attr->counter = entry->counter->counter;
attr->flags |= MLX5_ESW_ATTR_FLAG_NO_IN_PORT;
+ if (ct_priv->ns_type == MLX5_FLOW_NAMESPACE_FDB)
+ attr->esw_attr->in_mdev = priv->mdev;
mlx5_tc_ct_set_tuple_match(netdev_priv(ct_priv->netdev), spec, flow_rule);
mlx5e_tc_match_to_reg_match(spec, ZONE_TO_REG, entry->tuple.zone, MLX5_CT_ZONE_MASK);
--
2.29.2
next prev parent reply other threads:[~2021-02-05 6:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 6:40 [pull request][net-next 00/17] mlx5 updates 2021-02-04 Saeed Mahameed
2021-02-05 6:40 ` [net-next 01/17] net/mlx5: E-Switch, Refactor setting source port Saeed Mahameed
2021-02-05 6:40 ` [net-next 02/17] net/mlx5e: E-Switch, Maintain vhca_id to vport_num mapping Saeed Mahameed
2021-02-05 6:40 ` Saeed Mahameed [this message]
2021-02-05 6:40 ` [net-next 04/17] net/mlx5: E-Switch, Refactor rule offload forward action processing Saeed Mahameed
2021-02-05 6:40 ` [net-next 05/17] net/mlx5e: VF tunnel TX traffic offloading Saeed Mahameed
2021-02-05 6:40 ` [net-next 06/17] net/mlx5e: Refactor tun routing helpers Saeed Mahameed
2021-02-05 6:40 ` [net-next 07/17] net/mlx5: E-Switch, Indirect table infrastructure Saeed Mahameed
2021-02-05 6:40 ` [net-next 08/17] net/mlx5e: Remove redundant match on tunnel destination mac Saeed Mahameed
2021-02-05 6:40 ` [net-next 09/17] net/mlx5e: VF tunnel RX traffic offloading Saeed Mahameed
2021-02-05 6:40 ` [net-next 10/17] net/mlx5e: Refactor reg_c1 usage Saeed Mahameed
2021-02-05 6:40 ` [net-next 11/17] net/mlx5e: Match recirculated packet miss in slow table using reg_c1 Saeed Mahameed
2021-02-05 6:40 ` [net-next 12/17] net/mlx5e: Extract tc tunnel encap/decap code to dedicated file Saeed Mahameed
2021-02-05 6:40 ` [net-next 13/17] net/mlx5e: Create route entry infrastructure Saeed Mahameed
2021-02-05 6:40 ` [net-next 14/17] net/mlx5e: Refactor neigh update infrastructure Saeed Mahameed
2021-02-05 6:40 ` [net-next 15/17] net/mlx5e: TC preparation refactoring for routing update event Saeed Mahameed
2021-02-05 6:40 ` [net-next 16/17] net/mlx5e: Rename some encap-specific API to generic names Saeed Mahameed
2021-02-05 6:40 ` [net-next 17/17] net/mlx5e: Handle FIB events to update tunnel endpoint device Saeed Mahameed
2021-02-05 20:41 ` [pull request][net-next 00/17] mlx5 updates 2021-02-04 Jakub Kicinski
2021-02-06 5:00 ` Saeed Mahameed
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=20210205064051.89592-4-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=dlinkin@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@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).