All of
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <>
To: David Hildenbrand <>
Cc: Andrew Morton <>,
	Mel Gorman <>,, Vlastimil Babka <>,
	Peter Zijlstra <>,
	Thomas Gleixner <>
Date: Thu, 28 Oct 2021 18:17:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2021-10-28 17:54:01 [+0200], David Hildenbrand wrote:
> Makes perfect sense to me. I was also wondering how "dangerous"
> MIGRATION (and everything depending on it, like CMA, compaction,
> MEMORY_HOTREMOVE, ...) is for RT recently.

for compatcion there is
  6923aa0d8c629 ("mm/compaction: Disable compact_unevictable_allowed on RT")

to honour mlock() otherwise it can end unpleasant. But yeah, any page
migrations outside of the "setup/ init" phase of the RT task are bad.


      reply	other threads:[~2021-10-28 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 14:33 [PATCH] mm: Disable NUMA_BALANCING_DEFAULT_ENABLED and TRANSPARENT_HUGEPAGE on PREEMPT_RT Sebastian Andrzej Siewior
2021-10-28 14:37 ` Mel Gorman
2021-10-28 15:54 ` David Hildenbrand
2021-10-28 16:17   ` Sebastian Andrzej Siewior [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.