From: Alexander Krabler <Alexander.Krabler@kuka.com>
To: Hugh Dickins <hughd@google.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Frank van der Linden <fvdl@google.com>,
Mike Galbraith <efault@gmx.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Dennis Schimmel <Dennis.Schimmel@kuka.com>,
Daniel Braunwarth <Daniel.Braunwarth@kuka.com>
Subject: Re: Realtime threads delayed due to kcompactd0
Date: Thu, 7 Aug 2025 15:49:15 +0000 [thread overview]
Message-ID: <DU0PR01MB10385C55AEAFEBCA2575EAA77822CA@DU0PR01MB10385.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <771a8fc0-8195-44cc-55ed-c3573d497d2d@google.com>
On Thu, 7 Aug 2025 14:21, Hugh Dickins wrote:
> But another idea has just this moment occurred to me: anon THP splitting
> is another user of migration entries. Is it possible that kcompactd is
> not actually the cause of Alexander's issue, but that his RT tasks have
> (bad news! shouldn't be allowed) got anon THPs in them?
No, we don't have transparent hugepages enabled.
(From Kconfig, this seems not even possible together with PREEMPT_RT.)
From ftrace events (first message in this thread), we know that kcompactd0
finally wakes our realtime thread(s).
Given the information I got from here, the comment on the code [1]
and an older commit message [2], I suspect CMA somehow influences our problem.
If there is anything we should enable for better diagnosis (e.g. more ftrace events),
we would be willing to try that out.
[1] https://elixir.bootlin.com/linux/v6.16/source/mm/compaction.c#L1136
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e46a28790e594c0876d1a84270926abf75460f61
Thanks,
Alexander
--
KUKA Deutschland GmbH Board of Directors: Michael Jürgens (Chairman), Dirk Busch, Johan Naten, Hui Zhang Registered Office: Augsburg HRB 14914
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of contents of this e-mail is strictly forbidden.
Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2025-08-07 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 5:30 Alexander Krabler
2025-07-31 18:34 ` Frank van der Linden
2025-07-31 18:41 ` Vlastimil Babka
2025-08-01 2:46 ` Mike Galbraith
2025-08-01 9:58 ` Vlastimil Babka
2025-08-01 11:23 ` Alexander Krabler
2025-08-01 12:57 ` Vlastimil Babka
2025-08-01 13:40 ` Alexander Krabler
2025-08-07 10:48 ` Vlastimil Babka
2025-08-07 12:21 ` Hugh Dickins
2025-08-07 15:49 ` Alexander Krabler [this message]
2025-08-08 7:37 ` Vlastimil Babka
2025-08-20 14:29 ` Sebastian Andrzej Siewior
2025-08-01 19:27 ` Frank van der Linden
2025-08-05 14:11 ` Alexander Krabler
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=DU0PR01MB10385C55AEAFEBCA2575EAA77822CA@DU0PR01MB10385.eurprd01.prod.exchangelabs.com \
--to=alexander.krabler@kuka.com \
--cc=Daniel.Braunwarth@kuka.com \
--cc=Dennis.Schimmel@kuka.com \
--cc=efault@gmx.de \
--cc=fvdl@google.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=vbabka@suse.cz \
/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