linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@techsingularity.net>
Cc: linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] mm: Disable NUMA_BALANCING_DEFAULT_ENABLED and TRANSPARENT_HUGEPAGE on PREEMPT_RT
Date: Thu, 28 Oct 2021 17:54:01 +0200	[thread overview]
Message-ID: <53abed4c-a66b-9735-4411-c919ede8c47c@redhat.com> (raw)
In-Reply-To: <20211028143327.hfbxjze7palrpfgp@linutronix.de>

On 28.10.21 16:33, Sebastian Andrzej Siewior wrote:
> TRANSPARENT_HUGEPAGE:
> There are potential non-deterministic delays to an RT thread if a critical
> memory region is not THP-aligned and a non-RT buffer is located in the same
> hugepage-aligned region. It's also possible for an unrelated thread to migrate
> pages belonging to an RT task incurring unexpected page faults due to memory
> defragmentation even if khugepaged is disabled.
> 
> Regular HUGEPAGEs are not affected by this can be used.
> 
> NUMA_BALANCING:
> There is a non-deterministic delay to mark PTEs PROT_NONE to gather NUMA fault
> samples, increased page faults of regions even if mlocked and non-deterministic
> delays when migrating pages.
> 
> [Mel Gorman worded 99% of the commit description].
> 
> Link: https://lore.kernel.org/all/20200304091159.GN3818@techsingularity.net/
> Link: https://lore.kernel.org/all/20211026165100.ahz5bkx44lrrw5pt@linutronix.de/
> Cc: Mel Gorman <mgorman@techsingularity.net>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  init/Kconfig | 2 +-
>  mm/Kconfig   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index edc0a0228f143..f83e7a0478f7c 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -911,7 +911,7 @@ config NUMA_BALANCING
>  	bool "Memory placement aware NUMA scheduler"
>  	depends on ARCH_SUPPORTS_NUMA_BALANCING
>  	depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
> -	depends on SMP && NUMA && MIGRATION
> +	depends on SMP && NUMA && MIGRATION && !PREEMPT_RT
>  	help
>  	  This option adds support for automatic NUMA aware memory/task placement.
>  	  The mechanism is quite primitive and is based on migrating memory when
> diff --git a/mm/Kconfig b/mm/Kconfig
> index c150a0c6fce2c..5c5508fafcec5 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -374,7 +374,7 @@ config NOMMU_INITIAL_TRIM_EXCESS
>  
>  config TRANSPARENT_HUGEPAGE
>  	bool "Transparent Hugepage Support"
> -	depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE
> +	depends on HAVE_ARCH_TRANSPARENT_HUGEPAGE && !PREEMPT_RT
>  	select COMPACTION
>  	select XARRAY_MULTI
>  	help
> 

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.

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb



  parent reply	other threads:[~2021-10-28 15:54 UTC|newest]

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

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=53abed4c-a66b-9735-4411-c919ede8c47c@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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