From: Andrew Morton <akpm@linux-foundation.org>
To: craftfever@tutamail.com
Cc: bugzilla-daemon@kernel.org, linux-mm@kvack.org,
David Hildenbrand <david@redhat.com>,
Xu Xin <xu.xin16@zte.com.cn>,
Chengming Zhou <chengming.zhou@linux.dev>
Subject: Re: [Bug 220599] New: KSM performance degradation after Linux 6.16 update
Date: Wed, 24 Sep 2025 15:03:56 -0700 [thread overview]
Message-ID: <20250924150356.3d615a8a4481b817f2794848@linux-foundation.org> (raw)
In-Reply-To: <bug-220599-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 24 Sep 2025 09:36:44 +0000 bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220599
There are more details at the above link.
> Bug ID: 220599
> Summary: KSM performance degradation after Linux 6.16 update
> Product: Memory Management
> Version: 2.5
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Other
> Assignee: akpm@linux-foundation.org
> Reporter: craftfever@tutamail.com
> Regression: No
>
> After updating to Linux 6.16, I'm expecting freezing, particularly with
> Chromium applications, when usind KSM with MemoryKSM setting. ksmd kernel
> thread spikes to 100% cpu usage, with console and chromium apps freeze, which
> not the case with linux<=6.15.x. I believe this happens, 'cause chromium-based
> apps using V8 sandbox with huge virtual memory size, but, again, it's alright
> on linux 6.15 or earlier. With Linux 6.16 it's a nightmare.
Thanks.
Please prefer to report issues via email - we don't use the bugzilla
thing and I rather wish it didn't exist.
parent reply other threads:[~2025-09-24 22:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-220599-27@https.bugzilla.kernel.org/>]
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=20250924150356.3d615a8a4481b817f2794848@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=craftfever@tutamail.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=xu.xin16@zte.com.cn \
/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