[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <277314c9-c4aa-4966-9fbe-c5c42feed7ef@gmail.com>
Date: Sun, 11 Aug 2024 10:08:59 +0200
From: Jannik Glückert <jannik.glueckert@...il.com>
To: fdmanana@...nel.org
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
Hello,
I am still encountering this issue on 6.10.3. As far as I can see this
is the last post in the thread, if the discussion continued elsewhere
please let me know.
My workload is a backup via restic, the system is idle otherwise.
This is on a Zen4 CPU with a very fast PCIe Gen4 nvme, so perhaps it was
fixed for others because they had comparatively slow IO or a smaller
workload?
I have attached the bpftrace run and a graph of the memory PSI. kswapd0
is at 100% during the critical sections. dmesg is empty.
Important events were e.g. 09:31-09:32 and 09:33-09:34 where the system
was completely unresponsive multiple times, for about 5 seconds at a time.
I did also mention this on the #btrfs IRC channel and there are other
users still encountering this on 6.10
Best
Jannik
Download attachment "psi_memory.jpg" of type "image/jpeg" (297648 bytes)
Download attachment "bpftrace.log.gz" of type "application/gzip" (178863 bytes)
Powered by blists - more mailing lists