aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/drivers/net/hw/pp_alloc_fail.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-10-07 16:26:50 -0700
committerPaolo Abeni <pabeni@redhat.com>2025-10-09 11:10:02 +0200
commit2eecd3a41e67c03e52905c42a1e19cc6266a608a (patch)
treee46998da47623a85bff8d0a027386a72493d568e /tools/testing/selftests/drivers/net/hw/pp_alloc_fail.py
parentselftests: drv-net: xdp: add test for interface level qstats (diff)
downloadlinux-2eecd3a41e67c03e52905c42a1e19cc6266a608a.tar.gz
linux-2eecd3a41e67c03e52905c42a1e19cc6266a608a.zip
eth: fbnic: fix reporting of alloc_failed qstats
Rx processing under normal circumstances has 3 rings - 2 buffer rings (heads, payloads) and a completion ring. All the rings have a struct fbnic_ring. Make sure we expose alloc_failed counter from the buffer rings, previously only the alloc_failed from the completion ring was reported, even tho all ring types may increment this counter (buffer rings in __fbnic_fill_bdq()). This makes the pp_alloc_fail.py test pass, it expects the qstat to be incrementing as page pool injections happen. Reviewed-by: Simon Horman <horms@kernel.org> Fixes: 67dc4eb5fc92 ("eth: fbnic: report software Rx queue stats") Signed-off-by: Jakub Kicinski <kuba@kernel.org> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com> Link: https://patch.msgid.link/20251007232653.2099376-7-kuba@kernel.org Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/testing/selftests/drivers/net/hw/pp_alloc_fail.py')
0 files changed, 0 insertions, 0 deletions