aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAlexei Lazar <alazar@nvidia.com>2025-08-20 16:32:08 +0300
committerJakub Kicinski <kuba@kernel.org>2025-08-21 07:58:32 -0700
commit451d2849ea66659040b59ae3cb7e50cc97404733 (patch)
treeba1a344fd32eca087843131550d12ecd801b29bd /tools/perf/scripts/python
parentnet/mlx5: Restore missing scheduling node cleanup on vport enable failure (diff)
downloadwireguard-linux-451d2849ea66659040b59ae3cb7e50cc97404733.tar.xz
wireguard-linux-451d2849ea66659040b59ae3cb7e50cc97404733.zip
net/mlx5e: Query FW for buffer ownership
The SW currently saves local buffer ownership when setting the buffer. This means that the SW assumes it has ownership of the buffer after the command is set. If setting the buffer fails and we remain in FW ownership, the local buffer ownership state incorrectly remains as SW-owned. This leads to incorrect behavior in subsequent PFC commands, causing failures. Instead of saving local buffer ownership in SW, query the FW for buffer ownership when setting the buffer. This ensures that the buffer ownership state is accurately reflected, avoiding the issues caused by incorrect ownership states. Fixes: ecdf2dadee8e ("net/mlx5e: Receive buffer support for DCBX") Signed-off-by: Alexei Lazar <alazar@nvidia.com> Reviewed-by: Shahar Shitrit <shshitrit@nvidia.com> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com> Signed-off-by: Mark Bloch <mbloch@nvidia.com> Link: https://patch.msgid.link/20250820133209.389065-8-mbloch@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions