From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/6] fix test failures on larger core systems
Date: Mon, 19 Jan 2026 17:55:03 -0800 [thread overview]
Message-ID: <20260120015759.301155-1-stephen@networkplumber.org> (raw)
In-Reply-To: <0260118201223.323024-1-stephen@networkplumber.org>
This series addresses several test failures that occur sporadically on
systems with many cores (32+), particularly on AMD Zen architectures.
I think Ferruh may have addressed similar problems in earlier
releases.
The root causes fall into three categories:
1. Missing rte_pause() in synchronization spinloops (patch 1)
Tight spinloops without pause cause SMT thread starvation and
unpredictable timing behavior.
2. Fixed iteration counts that don't scale (patch 2)
The atomic test performs 1M iterations per worker regardless of
core count. With 32+ cores, contention causes timeout failures.
3. File-prefix collisions during parallel test execution (patches 5-6)
Multiple tests using the default "rte" prefix compete for the same
fbarray files, causing EAL initialization failures.
Additionally, two BPF-related fixes that I was seeing on
this system.
4. Lack of error checking in BPF elf load test (patch 3)
5. Unsupported BPF instructions with newer clang (patch 4)
Clang 20+ generates JMP32 instructions that DPDK BPF doesn't support.
v2 - Drop the unnecessary fsync()
- Rework the file prefix handling for trace tests
Stephen Hemminger (6):
test: add pause to synchronization spinloops
test: fix timeout for atomic test on high core count systems
test: fix error handling in ELF load tests
test: fix unsupported BPF instructions in elf load test
test: add file-prefix for all fast-tests on Linux
test: fix trace_autotest_with_traces parallel execution
app/test/bpf/meson.build | 3 +-
app/test/suites/meson.build | 23 +++++++++----
app/test/test_atomic.c | 67 ++++++++++++++++++++++---------------
app/test/test_bpf.c | 3 +-
app/test/test_threads.c | 17 +++++-----
5 files changed, 70 insertions(+), 43 deletions(-)
--
2.51.0
next parent reply other threads:[~2026-01-20 1:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0260118201223.323024-1-stephen@networkplumber.org>
2026-01-20 1:55 ` Stephen Hemminger [this message]
2026-01-20 1:55 ` [PATCH v2 1/6] test: add pause to synchronization spinloops Stephen Hemminger
2026-01-21 16:10 ` Bruce Richardson
2026-01-20 1:55 ` [PATCH v2 2/6] test: fix timeout for atomic test on high core count systems Stephen Hemminger
2026-01-21 16:11 ` Bruce Richardson
2026-01-20 1:55 ` [PATCH v2 3/6] test: fix error handling in ELF load tests Stephen Hemminger
2026-01-20 12:08 ` Marat Khalili
2026-01-20 1:55 ` [PATCH v2 4/6] test: fix unsupported BPF instructions in elf load test Stephen Hemminger
2026-01-21 16:20 ` Bruce Richardson
2026-01-20 1:55 ` [PATCH v2 5/6] test: add file-prefix for all fast-tests on Linux Stephen Hemminger
2026-01-21 16:22 ` Bruce Richardson
2026-01-20 1:55 ` [PATCH v2 6/6] test: fix trace_autotest_with_traces parallel execution Stephen Hemminger
2026-01-21 16:29 ` Bruce Richardson
2026-01-21 16:31 ` [PATCH v2 0/6] fix test failures on larger core systems Bruce Richardson
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=20260120015759.301155-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox