[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eaef24be-0dce-446a-9eb7-5ae155345c9c@kernel.org>
Date: Tue, 14 Jan 2025 15:18:36 +0100
From: Matthieu Baerts <matttbe@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Netdev <netdev@...r.kernel.org>, MPTCP Linux <mptcp@...ts.linux.dev>
Subject: Re: [TEST] mptcp-connect
Hi Jakub,
On 13/01/2025 20:44, Jakub Kicinski wrote:
> 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.
Good to know, thank you.
>> 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 :)
Good idea :)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists