diff options
| author |   Dragos Tatulea <dtatulea@nvidia.com> | 2024-11-07 21:43:53 +0200 |
|---|---|---|
| committer |   Jakub Kicinski <kuba@kernel.org> | 2024-11-11 19:28:18 -0800 |
| commit | 8a0ee54027b1fbccda3f2683dafec9b7216993a4 (patch) | |
| tree | 86d0f79251b5ddc0302287e00d53a3117260d66c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | net/mlx5: Make vport QoS enablement more flexible for future extensions (diff) | |
| download | wireguard-linux-8a0ee54027b1fbccda3f2683dafec9b7216993a4.tar.xz wireguard-linux-8a0ee54027b1fbccda3f2683dafec9b7216993a4.zip | |
net/mlx5e: SHAMPO, Simplify UMR allocation for headers
Allocating page fragments for header data split is currently
more complicated than it should be. That's because the number
of KSM entries allocated is not aligned to the number of headers
per page. This leads to having leftovers in the next allocation
which require additional accounting and needlessly complicated
code.
This patch aligns (down) the number of KSM entries in the
UMR WQE to the number of headers per page by:
1) Aligning the max number of entries allocated per UMR WQE
(max_ksm_entries) to MLX5E_SHAMPO_WQ_HEADER_PER_PAGE.
2) Aligning the total number of free headers to
MLX5E_SHAMPO_WQ_HEADER_PER_PAGE.
... and then it drops the extra accounting code from
mlx5e_build_shampo_hd_umr().
Although the number of entries allocated per UMR WQE is slightly
smaller due to aligning down, no performance impact was observed.
Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20241107194357.683732-9-tariqt@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions