From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Soham Chakradeo <sohamch.kernel@gmail.com>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
linux-kselftest@vger.kernel.org,
Soham Chakradeo <sohamch@google.com>
Subject: Re: [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests
Date: Thu, 19 Dec 2024 18:01:44 -0800 [thread overview]
Message-ID: <20241219180144.7cf5226c@kernel.org> (raw)
In-Reply-To: <676474a0398f0_1f2e51294ad@willemb.c.googlers.com.notmuch>
On Thu, 19 Dec 2024 14:31:44 -0500 Willem de Bruijn wrote:
> All three timestamping flakes are instances where the script expects
> the timestamp to be taken essentially instantaneously after the send
> call.
>
> This is not the case, and the delay is outside even the 14K tolerance.
> I see occurrences of 20K. At some point we cannot keep increasing the
> tolerance, perhaps.
I pinned the other services away and gave the packetdrill tester its
own cores. Let's see how much of a difference this makes.
The net-next-2024-12-20--03-00 branch will be the first to have this.
next prev parent reply other threads:[~2024-12-20 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 18:51 [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests Soham Chakradeo
2024-12-17 18:51 ` [PATCH net-next 1/4] selftests/net: packetdrill: import tcp/ecn, tcp/close, tcp/sack, tcp/tcp_info Soham Chakradeo
2024-12-17 18:51 ` [PATCH net-next 2/4] selftests/net: packetdrill: import tcp/fast_recovery, tcp/nagle, tcp/timestamping Soham Chakradeo
2024-12-17 18:52 ` [PATCH net-next 3/4] selftests/net: packetdrill: import tcp/eor, tcp/splice, tcp/ts_recent, tcp/blocking Soham Chakradeo
2024-12-17 18:52 ` [PATCH net-next 4/4] selftests/net: packetdrill: import tcp/user_timeout, tcp/validate, tcp/sendfile, tcp/limited-transmit, tcp/syscall_bad_arg Soham Chakradeo
2024-12-18 18:00 ` [PATCH net-next 0/4] selftests/net: packetdrill: import multiple tests Jakub Kicinski
2024-12-18 19:43 ` Willem de Bruijn
2024-12-19 8:54 ` Paolo Abeni
2024-12-19 19:31 ` Willem de Bruijn
2024-12-20 2:01 ` Jakub Kicinski [this message]
2024-12-23 3:46 ` Willem de Bruijn
2024-12-23 16:50 ` Jakub Kicinski
2024-12-24 15:59 ` Willem de Bruijn
2024-12-27 18:41 ` Jakub Kicinski
2024-12-18 18:10 ` patchwork-bot+netdevbpf
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=20241219180144.7cf5226c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sohamch.kernel@gmail.com \
--cc=sohamch@google.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).