Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Bloch <mbloch@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch, horms@kernel.org,
	saeedm@nvidia.com, gal@nvidia.com, leonro@nvidia.com,
	tariqt@nvidia.com, leon@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 00/10] net/mlx5: HWS, Optimize matchers ICM usage
Date: Tue, 08 Jul 2025 02:20:52 +0000	[thread overview]
Message-ID: <175194125285.3546943.3231273757948141290.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250703185431.445571-1-mbloch@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 3 Jul 2025 21:54:21 +0300 you wrote:
> This series optimizes ICM usage for unidirectional rules and
> empty matchers and with the last patch we make hardware steering
> the default FDB steering provider for NICs that don't support software
> steering.
> 
> Hardware steering (HWS) uses a type of rule table container (RTC) that
> is unidirectional, so matchers consist of two RTCs to accommodate
> bidirectional rules.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/10] net/mlx5: HWS, remove unused create_dest_array parameter
    https://git.kernel.org/netdev/net-next/c/60afb51c8941
  - [net-next,v3,02/10] net/mlx5: HWS, remove incorrect comment
    https://git.kernel.org/netdev/net-next/c/26b06579d50d
  - [net-next,v3,03/10] net/mlx5: HWS, Export rule skip logic
    https://git.kernel.org/netdev/net-next/c/d8e7ab591b50
  - [net-next,v3,04/10] net/mlx5: HWS, Refactor rule skip logic
    https://git.kernel.org/netdev/net-next/c/3dcac700d20b
  - [net-next,v3,05/10] net/mlx5: HWS, Create STEs directly from matcher
    https://git.kernel.org/netdev/net-next/c/59807d071724
  - [net-next,v3,06/10] net/mlx5: HWS, Decouple matcher RX and TX sizes
    https://git.kernel.org/netdev/net-next/c/c8332ce09691
  - [net-next,v3,07/10] net/mlx5: HWS, Track matcher sizes individually
    https://git.kernel.org/netdev/net-next/c/6b44fffdc7b7
  - [net-next,v3,08/10] net/mlx5: HWS, Rearrange to prevent forward declaration
    https://git.kernel.org/netdev/net-next/c/29063103f864
  - [net-next,v3,09/10] net/mlx5: HWS, Shrink empty matchers
    https://git.kernel.org/netdev/net-next/c/96e4c4a1a5bc
  - [net-next,v3,10/10] net/mlx5: Add HWS as secondary steering mode
    https://git.kernel.org/netdev/net-next/c/a9aec713d0d9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-07-08  2:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 18:54 [PATCH net-next v3 00/10] net/mlx5: HWS, Optimize matchers ICM usage Mark Bloch
2025-07-03 18:54 ` [PATCH net-next v3 01/10] net/mlx5: HWS, remove unused create_dest_array parameter Mark Bloch
2025-07-03 18:54 ` [PATCH net-next v3 02/10] net/mlx5: HWS, remove incorrect comment Mark Bloch
2025-07-03 18:54 ` [PATCH net-next v3 03/10] net/mlx5: HWS, Export rule skip logic Mark Bloch
2025-07-07 11:08   ` Simon Horman
2025-07-03 18:54 ` [PATCH net-next v3 04/10] net/mlx5: HWS, Refactor " Mark Bloch
2025-07-07 11:08   ` Simon Horman
2025-07-03 18:54 ` [PATCH net-next v3 05/10] net/mlx5: HWS, Create STEs directly from matcher Mark Bloch
2025-07-03 18:54 ` [PATCH net-next v3 06/10] net/mlx5: HWS, Decouple matcher RX and TX sizes Mark Bloch
2025-07-03 18:54 ` [PATCH net-next v3 07/10] net/mlx5: HWS, Track matcher sizes individually Mark Bloch
2025-07-07 11:09   ` Simon Horman
2025-07-03 18:54 ` [PATCH net-next v3 08/10] net/mlx5: HWS, Rearrange to prevent forward declaration Mark Bloch
2025-07-07 11:09   ` Simon Horman
2025-07-03 18:54 ` [PATCH net-next v3 09/10] net/mlx5: HWS, Shrink empty matchers Mark Bloch
2025-07-07 11:09   ` Simon Horman
2025-07-03 18:54 ` [PATCH net-next v3 10/10] net/mlx5: Add HWS as secondary steering mode Mark Bloch
2025-07-07 11:10   ` Simon Horman
2025-07-08  2:20 ` 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=175194125285.3546943.3231273757948141290.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@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