From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 00/11] mlxsw: Move allocation of LAG table to the driver
Date: Fri, 20 Oct 2023 10:50:25 +0000 [thread overview]
Message-ID: <169779902581.4905.8675281223020212534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1697710282.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 19 Oct 2023 12:27:09 +0200 you wrote:
> PGT is an in-HW table that maps addresses to sets of ports. Then when some
> HW process needs a set of ports as an argument, instead of embedding the
> actual set in the dynamic configuration, what gets configured is the
> address referencing the set. The HW then works with the appropriate PGT
> entry.
>
> Within the PGT is placed a LAG table. That is a contiguous block of PGT
> memory where each entry describes which ports are members of the
> corresponding LAG port.
>
> [...]
Here is the summary with links:
- [net-next,01/11] mlxsw: reg: Drop SGCR.llb
https://git.kernel.org/netdev/net-next/c/66eaaa85418b
- [net-next,02/11] mlxsw: reg: Add SGCR.lag_lookup_pgt_base
https://git.kernel.org/netdev/net-next/c/cf0a86e8ce60
- [net-next,03/11] mlxsw: cmd: Fix omissions in CONFIG_PROFILE field names in comments
https://git.kernel.org/netdev/net-next/c/be9ed47d3fab
- [net-next,04/11] mlxsw: cmd: Add CONFIG_PROFILE.{set_, }lag_mode
https://git.kernel.org/netdev/net-next/c/eb26a5923277
- [net-next,05/11] mlxsw: cmd: Add QUERY_FW.lag_mode_support
https://git.kernel.org/netdev/net-next/c/8eabd10cdce4
- [net-next,06/11] mlxsw: core, pci: Add plumbing related to LAG mode
https://git.kernel.org/netdev/net-next/c/b2e9b1fe8c2e
- [net-next,07/11] mlxsw: pci: Permit toggling LAG mode
https://git.kernel.org/netdev/net-next/c/daee7aaba849
- [net-next,08/11] mlxsw: spectrum_fid: Allocate PGT for the whole FID family in one go
https://git.kernel.org/netdev/net-next/c/f5e293f9939e
- [net-next,09/11] mlxsw: spectrum_pgt: Generalize PGT allocation
https://git.kernel.org/netdev/net-next/c/8c893abd64ae
- [net-next,10/11] mlxsw: spectrum: Allocate LAG table when in SW LAG mode
https://git.kernel.org/netdev/net-next/c/c678972580ae
- [net-next,11/11] mlxsw: spectrum: Set SW LAG mode on Spectrum>1
https://git.kernel.org/netdev/net-next/c/b46c1f3f5e07
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:[~2023-10-20 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 10:27 [PATCH net-next 00/11] mlxsw: Move allocation of LAG table to the driver Petr Machata
2023-10-19 10:27 ` [PATCH net-next 01/11] mlxsw: reg: Drop SGCR.llb Petr Machata
2023-10-19 10:27 ` [PATCH net-next 02/11] mlxsw: reg: Add SGCR.lag_lookup_pgt_base Petr Machata
2023-10-19 10:27 ` [PATCH net-next 03/11] mlxsw: cmd: Fix omissions in CONFIG_PROFILE field names in comments Petr Machata
2023-10-19 10:27 ` [PATCH net-next 04/11] mlxsw: cmd: Add CONFIG_PROFILE.{set_, }lag_mode Petr Machata
2023-10-19 10:27 ` [PATCH net-next 05/11] mlxsw: cmd: Add QUERY_FW.lag_mode_support Petr Machata
2023-10-19 10:27 ` [PATCH net-next 06/11] mlxsw: core, pci: Add plumbing related to LAG mode Petr Machata
2023-10-19 10:27 ` [PATCH net-next 07/11] mlxsw: pci: Permit toggling " Petr Machata
2023-10-19 10:27 ` [PATCH net-next 08/11] mlxsw: spectrum_fid: Allocate PGT for the whole FID family in one go Petr Machata
2023-10-19 10:27 ` [PATCH net-next 09/11] mlxsw: spectrum_pgt: Generalize PGT allocation Petr Machata
2023-10-19 10:27 ` [PATCH net-next 10/11] mlxsw: spectrum: Allocate LAG table when in SW LAG mode Petr Machata
2023-10-19 10:27 ` [PATCH net-next 11/11] mlxsw: spectrum: Set SW LAG mode on Spectrum>1 Petr Machata
2023-10-20 10:50 ` 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=169779902581.4905.8675281223020212534.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@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).