summaryrefslogtreecommitdiffstats
path: root/net/core/devlink.c
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2022-08-30 23:20:55 -0700
committerJakub Kicinski <kuba@kernel.org>2022-08-30 23:20:56 -0700
commitd5ccda920ab3a61917cd19582204fdba669b221c (patch)
tree15b06f1052ea38ad45f4e60907e3963ce3edabed /net/core/devlink.c
parentfa8724478e64dcf6a45de9067004dcca07244934 (diff)
parentc503d8ae48f2443345ba82ef66a9dfc22389a66f (diff)
downloadlinux-d5ccda920ab3a61917cd19582204fdba669b221c.tar.bz2
Merge branch 'mlxsw-configure-max-lag-id-for-spectrum-4'
Petr Machata says: ==================== mlxsw: Configure max LAG ID for Spectrum-4 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. Therefore, in order to avoid a regression and as long as there is no explicit requirement to support 256 LAGs, configure the firmware to allocate the same amount of LAG entries (128) as in Spectrum-{2,3}. This can be done via the 'max_lag' field in CONFIG_PROFILE command. Patch set overview: Patch #1 edits the comment of the existing 'max_lag' field. Patch #2 adds support for configuring 'max_lag' field via CONFIG_PROFILE command. Patch #3 adds an helper function to get the actual 'max_lag' in the device. Patch #4 adjusts Spectrum-4 to configure 'max_lag' field. ==================== Link: https://lore.kernel.org/r/cover.1661527928.git.petrm@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/core/devlink.c')
0 files changed, 0 insertions, 0 deletions