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,
amcohen@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/4] mlxsw: Configure max LAG ID for Spectrum-4
Date: Wed, 31 Aug 2022 06:30:17 +0000 [thread overview]
Message-ID: <166192741785.4297.16962887795011276082.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1661527928.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 26 Aug 2022 18:06:48 +0200 you wrote:
> Amit Cohen writes:
>
> In the device, LAG identifiers are stored in the port group table (PGT).
> During initialization, firmware reserves a certain amount of entries at
> the beginning of this table for LAG identifiers.
>
> In Spectrum-4, the size of the PGT table did not increase, but the
> maximum number of LAG identifiers was doubled, leaving less room for
> others entries (e.g., flood entries) that also reside in the PGT.
>
> [...]
Here is the summary with links:
- [net-next,1/4] mlxsw: cmd: Edit the comment of 'max_lag' field in CONFIG_PROFILE
https://git.kernel.org/netdev/net-next/c/95484760f03d
- [net-next,2/4] mlxsw: Support configuring 'max_lag' via CONFIG_PROFILE
https://git.kernel.org/netdev/net-next/c/eb907e9779ca
- [net-next,3/4] mlxsw: Add a helper function for getting maximum LAG ID
https://git.kernel.org/netdev/net-next/c/cf735d4c9bab
- [net-next,4/4] mlxsw: spectrum: Add a copy of 'struct mlxsw_config_profile' for Spectrum-4
https://git.kernel.org/netdev/net-next/c/c503d8ae48f2
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:[~2022-08-31 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:06 [PATCH net-next 0/4] mlxsw: Configure max LAG ID for Spectrum-4 Petr Machata
2022-08-26 16:06 ` [PATCH net-next 1/4] mlxsw: cmd: Edit the comment of 'max_lag' field in CONFIG_PROFILE Petr Machata
2022-08-26 16:06 ` [PATCH net-next 2/4] mlxsw: Support configuring 'max_lag' via CONFIG_PROFILE Petr Machata
2022-08-26 16:06 ` [PATCH net-next 3/4] mlxsw: Add a helper function for getting maximum LAG ID Petr Machata
2022-08-26 16:06 ` [PATCH net-next 4/4] mlxsw: spectrum: Add a copy of 'struct mlxsw_config_profile' for Spectrum-4 Petr Machata
2022-08-31 6:30 ` 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=166192741785.4297.16962887795011276082.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.