From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemb@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] txtimestamp.sh pains after netdev foundation migration
Date: Wed, 7 Jan 2026 11:05:21 -0800 [thread overview]
Message-ID: <20260107110521.1aab55e9@kernel.org> (raw)
Hi Willem!
We discussed instability of txtimestamp.sh in the past but it has
gotten even worse after we migrated from AWS to netdev foundation
machines. Possibly because it's different HW. Possibly because we
now run much newer kernels (AWS Linux vs Fedora).
The test flakes a lot (we're talking about non-debug builds):
https://netdev.bots.linux.dev/contest.html?test=txtimestamp-sh
I tried a few things. The VM threads (vCPU, not IO) are now all pinned
to dedicated CPUs. I added this patch to avoid long idle periods:
https://github.com/linux-netdev/testing/commit/d468f582c617adece2a576788746a09d91e91574
These both help a little bit, but w still get 10+ flakes a week.
I believe you have access to netdev foundation machines so feel
free to poke if you have cycles..
next reply other threads:[~2026-01-07 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 19:05 Jakub Kicinski [this message]
2026-01-08 0:19 ` [TEST] txtimestamp.sh pains after netdev foundation migration Willem de Bruijn
2026-01-08 3:25 ` Jakub Kicinski
2026-01-08 16:06 ` Jakub Kicinski
2026-01-08 19:02 ` Willem de Bruijn
2026-01-08 20:38 ` Jakub Kicinski
2026-01-08 21:19 ` Willem de Bruijn
2026-01-12 3:24 ` Willem de Bruijn
2026-01-12 3:28 ` Willem de Bruijn
2026-01-12 14:29 ` Jakub Kicinski
2026-01-12 16:38 ` Willem de Bruijn
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=20260107110521.1aab55e9@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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