From: intelfx@intelfx.name
To: "Filipe Manana" <fdmanana@kernel.org>,
"Jannik Glückert" <jannik.glueckert@gmail.com>
Cc: andrea.gelmini@gmail.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
mikhail.v.gavrilov@gmail.com, regressions@lists.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
Date: Fri, 16 Aug 2024 00:21:20 +0200 [thread overview]
Message-ID: <3df4acd616a07ef4d2dc6bad668701504b412ffc.camel@intelfx.name> (raw)
In-Reply-To: <CAL3q7H4iYRsjG9BvRYh_aB6UN-QFuTCqJdiq6hV_Xh7+U7qJ5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
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 /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next prev parent reply other threads:[~2024-08-15 22:21 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 20:56 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory Mikhail Gavrilov
2024-06-26 10:48 ` Filipe Manana
2024-06-26 14:16 ` Mikhail Gavrilov
2024-07-01 9:30 ` Filipe Manana
2024-07-02 14:13 ` Mikhail Gavrilov
2024-07-02 17:22 ` Filipe Manana
2024-07-02 19:46 ` Chris Murphy
2024-07-03 10:32 ` Filipe Manana
2024-07-03 10:31 ` Filipe Manana
2024-07-03 10:44 ` Filipe Manana
2024-07-03 21:07 ` Andrea Gelmini
2024-07-04 9:48 ` Filipe Manana
2024-07-04 9:56 ` Filipe Manana
2024-07-04 10:50 ` Mikhail Gavrilov
2024-07-04 13:33 ` Andrea Gelmini
2024-07-04 13:47 ` Andrea Gelmini
2024-07-04 14:48 ` Andrea Gelmini
2024-07-04 17:25 ` Filipe Manana
2024-07-04 17:31 ` Filipe Manana
2024-07-04 22:15 ` Andrea Gelmini
2024-07-04 22:23 ` Andrea Gelmini
2024-07-05 11:00 ` Filipe Manana
2024-07-05 6:30 ` Andrea Gelmini
2024-07-05 11:06 ` Filipe Manana
2024-07-05 18:36 ` Mikhail Gavrilov
2024-07-05 23:09 ` Filipe Manana
2024-07-06 0:11 ` Andrea Gelmini
2024-07-06 12:07 ` Andrea Gelmini
2024-07-06 17:37 ` Filipe Manana
2024-07-07 9:41 ` Filipe Manana
2024-07-07 10:15 ` Andrea Gelmini
2024-07-07 10:28 ` Filipe Manana
2024-07-07 11:15 ` Andrea Gelmini
2024-07-07 12:10 ` Filipe Manana
2024-07-07 11:35 ` Mikhail Gavrilov
2024-07-07 12:15 ` Filipe Manana
2024-07-07 19:16 ` Mikhail Gavrilov
2024-07-08 14:15 ` Filipe Manana
2024-07-10 9:24 ` Mikhail Gavrilov
2024-07-10 10:53 ` Filipe Manana
2024-08-11 8:08 ` Jannik Glückert
2024-08-11 15:33 ` Filipe Manana
2024-08-14 21:24 ` Jannik Glückert
2024-08-15 22:21 ` intelfx [this message]
2024-08-15 23:17 ` intelfx
2024-08-16 0:02 ` David Sterba
2024-08-16 6:42 ` Andrea Gelmini
2024-08-16 6:47 ` Ivan Shapovalov
2024-08-16 7:45 ` Qu Wenruo
2024-08-16 10:58 ` Filipe Manana
2024-08-16 11:16 ` Ivan Shapovalov
2024-09-26 13:45 ` Filipe Manana
2024-07-04 11:18 ` Andrea Gelmini
2024-07-04 16:38 ` Filipe Manana
2024-07-04 22:32 ` Qu Wenruo
2024-07-05 6:18 ` Andrea Gelmini
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=3df4acd616a07ef4d2dc6bad668701504b412ffc.camel@intelfx.name \
--to=intelfx@intelfx.name \
--cc=andrea.gelmini@gmail.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=jannik.glueckert@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
/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