From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Netdev <netdev@vger.kernel.org>, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [TEST] mptcp-connect
Date: Mon, 13 Jan 2025 11:44:06 -0800 [thread overview]
Message-ID: <20250113114406.566f1072@kernel.org> (raw)
In-Reply-To: <22a1d42b-3015-47cf-b3d9-46d0ceb63ebc@kernel.org>
On Mon, 13 Jan 2025 17:08:02 +0100 Matthieu Baerts wrote:
> It was not easy to reproduce it, but Paolo managed to find a fix for it [1]!
>
> Out of curiosity, is the netdev CI not too overloaded? To reproduce this
> issue on my side, the host had to be quite busy: not dying with
> stress-ng using all resources, but still competing with many other
> processes, e.g. a kernel compilation running in parallel. I'm not
> complaining here, because this situation helped finding this important
> issue, but just curious about what to expect, especially for more
> "sensitive" tests :)
The tests my overlap with other workers still building their kernel.
ccache is enabled.
> On the MPTCP CI, some unessarry KConfig are disabled and ccache is used
> to reduce the build time. Also, RETPOLINE is disabled (+ vng --append
> mitigations=off) to save some CPU cycles during the tests.
Could help. Let's put it on the list of things to do once we migrate
the CI to a public set of hosts :)
next prev parent reply other threads:[~2025-01-13 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 21:18 [TEST] mptcp-connect Jakub Kicinski
2025-01-08 10:07 ` Matthieu Baerts
2025-01-13 16:08 ` Matthieu Baerts
2025-01-13 19:44 ` Jakub Kicinski [this message]
2025-01-14 14:18 ` Matthieu Baerts
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=20250113114406.566f1072@kernel.org \
--to=kuba@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.