netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	Christoph Paasch <cpaasch@openai.com>,
	Davide Caratti <dcaratti@redhat.com>,
	Florian Westphal <fw@strlen.de>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes
Date: Thu, 17 Jul 2025 07:42:42 -0700	[thread overview]
Message-ID: <20250717074242.1ef5d441@kernel.org> (raw)
In-Reply-To: <e46aadbf-51c6-4e09-bdaa-374698b406f3@kernel.org>

On Wed, 16 Jul 2025 18:35:11 +0200 Matthieu Baerts wrote:
> >> And just to be sure, no CPU or IO overload at that moment? I didn't see
> >> such errors reported by our CI, but I can try to reproduce them locally
> >> in different conditions.  
> > 
> > None that I can see. The test run ~10min after all the builds completed,
> > and we wait now for the CPU load to die down and writeback to finish
> > before we kick off VMs. The VMs for various tests are running at that
> > point, the CPU util averaged across cores is 66%.  
> 
> Thank you for having checked, and for the explanations!
> 
> OK, so maybe running stress-ng in parallel to be able to reproduce the
> issue might not help. We will investigate.

connect tests failed again overnight. Now I see why Paolo was
responding on Eric's series, that seems like a more likely culprit..

  reply	other threads:[~2025-07-17 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 18:43 [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes Matthieu Baerts (NGI0)
2025-07-15 18:43 ` [PATCH net v2 1/2] selftests: mptcp: connect: also " Matthieu Baerts (NGI0)
2025-07-15 18:43 ` [PATCH net v2 2/2] selftests: mptcp: connect: also cover checksum Matthieu Baerts (NGI0)
2025-07-16  1:53 ` [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes Jakub Kicinski
2025-07-16 14:26   ` Jakub Kicinski
2025-07-16 14:55     ` Matthieu Baerts
2025-07-16 15:36       ` Jakub Kicinski
2025-07-16 16:35         ` Matthieu Baerts
2025-07-17 14:42           ` Jakub Kicinski [this message]
2025-07-17 23:49             ` Matthieu Baerts
2025-07-18  1:33               ` Jakub Kicinski
2025-07-19  1:35                 ` Jakub Kicinski
2025-07-21 23:50 ` 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=20250717074242.1ef5d441@kernel.org \
    --to=kuba@kernel.org \
    --cc=cpaasch@openai.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).