[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3df4acd616a07ef4d2dc6bad668701504b412ffc.camel@intelfx.name>
Date: Fri, 16 Aug 2024 00:21:20 +0200
From: intelfx@...elfx.name
To: Filipe Manana <fdmanana@...nel.org>, Jannik Glückert
<jannik.glueckert@...il.com>
Cc: andrea.gelmini@...il.com, dsterba@...e.com, josef@...icpanda.com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
mikhail.v.gavrilov@...il.com, regressions@...ts.linux.dev
Subject: Re: 6.10/regression/bisected - after f1d97e769152 I spotted
increased execution time of the kswapd0 process and symptoms as if there is
not enough memory
On 2024-08-11 at 16:33 +0100, Filipe Manana wrote:
> <...>
> This came to my attention a couple days ago in a bugzilla report here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=219121
>
> There's also 2 other recent threads in the mailing about it.
>
> There's a fix there in the bugzilla, and I've just sent it to the mailing list.
> In case you want to try it:
>
> https://lore.kernel.org/linux-btrfs/d85d72b968a1f7b8538c581eeb8f5baa973dfc95.1723377230.git.fdmanana@suse.com/
>
> Thanks.
Hello,
I confirm that excessive "system" CPU usage by kswapd and btrfs-cleaner
kernel threads is still happening on the latest 6.10 stable with all
quoted patches applied, making the system close to unusable (not to
mention excessive power usage which crosses the line well *into*
"unusable" for low-power systems such as laptops).
With just 5 minutes of uptime on a freshly booted 6.10.5 system, the
cumulative CPU time of kswapd is already at 2 minutes.
Regards,
--
Ivan Shapovalov / intelfx /
Download attachment "signature.asc" of type "application/pgp-signature" (863 bytes)
Powered by blists - more mailing lists