From: patchwork-bot+netdevbpf@kernel.org
To: Alexandre Cassen <acassen@corp.free.fr>
Cc: saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com,
mbloch@nvidia.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
moshe@nvidia.com, kliteyn@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net/mlx5: less memory per offloaded tc rule
Date: Thu, 15 Oct 2026 10:00:05 +0000 [thread overview]
Message-ID: <179205840526.3325132.4078585050271061230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009052103.3621855-1-acassen@corp.free.fr>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 9 Oct 2026 07:20:59 +0200 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/mlx5e: TC, free NIC flow parse attributes after offload
https://git.kernel.org/netdev/net-next/c/dd0425c502fc
- [net-next,2/2] net/mlx5: HWS, shrink FTE action array to fit
https://git.kernel.org/netdev/net-next/c/3636705910f9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-15 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 5:20 [PATCH net-next 0/2] net/mlx5: less memory per offloaded tc rule Alexandre Cassen
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-14 13:01 ` Tariq Toukan
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
2026-10-14 13:02 ` Tariq Toukan
2026-10-15 10:00 ` patchwork-bot+netdevbpf [this message]
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=179205840526.3325132.4078585050271061230.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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