netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>
Cc: <netdev@vger.kernel.org>, Saeed Mahameed <saeedm@nvidia.com>,
	Gal Pressman <gal@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>, Chris Mi <cmi@nvidia.com>,
	Roi Dayan <roid@nvidia.com>, Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH net-next 01/11] net/mlx5: E-Switch, Increase max int port number for offload
Date: Tue, 6 Aug 2024 15:57:54 +0300	[thread overview]
Message-ID: <20240806125804.2048753-2-tariqt@nvidia.com> (raw)
In-Reply-To: <20240806125804.2048753-1-tariqt@nvidia.com>

From: Chris Mi <cmi@nvidia.com>

Currently MLX5E_TC_MAX_INT_PORT_NUM is 8. Usually int port has one
ingress and one egress rules. But sometimes, a temporary rule can be
offloaded as well, eg:

recirc_id(0),in_port(br-phy),eth(src=10:70:fd:87:57:c0,dst=33:33:00:00:00:16),
	eth_type(0x86dd),ipv6(frag=no), packets:2, bytes:180, used:0.060s,
	actions:enp8s0f0

If one int port device offloads 3 rules, only 2 devices can offload.
Other devices will hit the limit and fail to offload. Actually it is
insufficient for customers. So increase the number to 32.

Signed-off-by: Chris Mi <cmi@nvidia.com>
Reviewed-by: Roi Dayan <roid@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
---
 drivers/net/ethernet/mellanox/mlx5/core/en_tc.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.h b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.h
index c24bda56b2b5..b982e648ea48 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.h
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.h
@@ -139,7 +139,7 @@ struct mlx5_rx_tun_attr {
 #define MLX5E_TC_TABLE_CHAIN_TAG_BITS 16
 #define MLX5E_TC_TABLE_CHAIN_TAG_MASK GENMASK(MLX5E_TC_TABLE_CHAIN_TAG_BITS - 1, 0)
 
-#define MLX5E_TC_MAX_INT_PORT_NUM (8)
+#define MLX5E_TC_MAX_INT_PORT_NUM (32)
 
 #if IS_ENABLED(CONFIG_MLX5_CLS_ACT)
 
-- 
2.44.0


  reply	other threads:[~2024-08-06 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 12:57 [PATCH net-next 00/11] mlx5 misc patches 2024-08-06 Tariq Toukan
2024-08-06 12:57 ` Tariq Toukan [this message]
2024-08-06 12:57 ` [PATCH net-next 02/11] net/mlx5e: Enable remove flow for hard packet limit Tariq Toukan
2024-08-06 12:57 ` [PATCH net-next 03/11] net/mlx5e: TC, Offload rewrite and mirror on tunnel over ovs internal port Tariq Toukan
2024-08-06 12:57 ` [PATCH net-next 04/11] net/mlx5e: TC, Offload rewrite and mirror to both internal and external dests Tariq Toukan
2024-08-06 12:57 ` [PATCH net-next 05/11] net/mlx5e: Be consistent with bitmap handling of link modes Tariq Toukan
2024-08-06 12:57 ` [PATCH net-next 06/11] net/mlx5e: Use extack in set ringparams callback Tariq Toukan
2024-08-07  1:16   ` Jakub Kicinski
2024-08-07  6:22     ` Gal Pressman
2024-08-06 12:58 ` [PATCH net-next 07/11] net/mlx5e: Use extack in get coalesce callback Tariq Toukan
2024-08-06 12:58 ` [PATCH net-next 08/11] net/mlx5e: Use extack in set " Tariq Toukan
2024-08-06 12:58 ` [PATCH net-next 09/11] net/mlx5e: Use extack in get module eeprom by page callback Tariq Toukan
2024-08-06 12:58 ` [PATCH net-next 10/11] net/mlx5e: CT: 'update' rules instead of 'replace' Tariq Toukan
2024-08-06 12:58 ` [PATCH net-next 11/11] net/mlx5e: CT: Update connection tracking steering entries Tariq Toukan

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=20240806125804.2048753-2-tariqt@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=cmi@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roid@nvidia.com \
    --cc=saeedm@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).