From: Alexandre Cassen <acassen@corp.free.fr>
To: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Moshe Shemesh <moshe@nvidia.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH net-next 0/2] net/mlx5: less memory per offloaded tc rule
Date: Fri, 9 Oct 2026 07:20:59 +0200 [thread overview]
Message-ID: <20261009052103.3621855-1-acassen@corp.free.fr> (raw)
Two mlx5 allocations hold more memory than an offloaded tc rule needs.
A NIC flow keeps a 4 KB allocation for parse attributes that nothing
reads after offload. An FTE under hardware steering keeps the 1 KB
action array it was built in while a rule rarely needs more than three
entries.
Freeing the first after offload saves 4 KB per NIC flow. Shrinking the
second saves about 1 KB per FTE under hardware steering.
Alexandre Cassen (2):
net/mlx5e: TC, free NIC flow parse attributes after offload
net/mlx5: HWS, shrink FTE action array to fit
.../net/ethernet/mellanox/mlx5/core/en_tc.c | 18 +++++++++++++-----
.../mellanox/mlx5/core/steering/hws/fs_hws.c | 10 +++++++++-
2 files changed, 22 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-09 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 5:20 Alexandre Cassen [this message]
2026-10-09 5:21 ` [PATCH net-next 1/2] net/mlx5e: TC, free NIC flow parse attributes after offload Alexandre Cassen
2026-10-10 15:42 ` Simon Horman
2026-10-09 5:21 ` [PATCH net-next 2/2] net/mlx5: HWS, shrink FTE action array to fit Alexandre Cassen
2026-10-10 15:42 ` Simon Horman
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=20261009052103.3621855-1-acassen@corp.free.fr \
--to=acassen@corp.free.fr \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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