archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Matt Fleming <>,
	Mel Gorman <>,
	Peter Zijlstra <>,
	Ingo Molnar <>,
	Juri Lelli <>,
	Vincent Guittot <>,
	Andrew Morton <>,
	Vlastimil Babka <>
Cc: Yoshinori Sato <>,
	Rich Felker <>, Gon Solo <>,,,,
	Geert Uytterhoeven <>
Subject: [PATCH 0/2] Fix NUMA without SMP
Date: Thu, 16 Sep 2021 10:42:41 +0200	[thread overview]
Message-ID: <> (raw)

	Hi all,

SuperH is the only architecture which still supports NUMA without SMP,
for good reasons (various memories scattered around the address space,
each with varying latencies).  This series fixes two build errors due to
variables and functions used by the NUMA code being provided by SMP-only
source files or sections.

These are compile-tested only, as the remote Migo-R is MIA.

Thanks for your comments!

Geert Uytterhoeven (2):
  mm: Move node_reclaim_distance to fix NUMA without SMP
  mm: Move fold_vm_numa_events() to fix NUMA without SMP

 kernel/sched/topology.c |  1 -
 mm/page_alloc.c         |  2 ++
 mm/vmstat.c             | 56 ++++++++++++++++++++---------------------
 3 files changed, 30 insertions(+), 29 deletions(-)




Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2021-09-16  8:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  8:42 Geert Uytterhoeven [this message]
2021-09-16  8:42 ` [PATCH 1/2] mm: Move node_reclaim_distance to fix NUMA without SMP Geert Uytterhoeven
2021-09-21 12:32   ` Mel Gorman
2021-09-16  8:42 ` [PATCH 2/2] mm: Move fold_vm_numa_events() " Geert Uytterhoeven
2021-09-21 12:33   ` Mel Gorman

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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).