From: Dan Williams <dan.j.williams@intel.com>
To: mingo@kernel.org
Cc: Wei Yang <richard.weiyang@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [PATCH 0/2] x86/numa_emulation: Introduce uniform split capability
Date: Sat, 26 May 2018 17:56:47 -0700 [thread overview]
Message-ID: <152738260746.11641.13275998345345705617.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
The current numa emulation capabilities for splitting System RAM by a
fixed size or by a set number of nodes may result in some nodes being
larger than others. The implementation prioritizes establishing a
minimum usable memory size over satisfying the requested number of numa
nodes.
Introduce a uniform split capability that evenly partitions each
physical numa node into N emulated nodes. For example numa=fake=3U
creates 6 emulated nodes total on a system that has 2 physical nodes.
This capability is useful for debugging and evaluating platform
memory-side-cache capabilities as described by the ACPI HMAT (see
5.2.27.5 Memory Side Cache Information Structure in ACPI 6.2a)
See more details in patch2.
---
Dan Williams (2):
x86/numa_emulation: Fix emulated-to-physical node mapping
x86/numa_emulation: Introduce uniform split capability
Documentation/x86/x86_64/boot-options.txt | 4 +
arch/x86/mm/numa_emulation.c | 98 +++++++++++++++++++++++------
2 files changed, 82 insertions(+), 20 deletions(-)
next reply other threads:[~2018-05-27 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 0:56 Dan Williams [this message]
2018-05-27 0:56 ` [PATCH 1/2] x86/numa_emulation: Fix emulated-to-physical node mapping Dan Williams
2018-05-27 0:56 ` [PATCH 2/2] x86/numa_emulation: Introduce uniform split capability Dan Williams
2018-08-16 12:54 ` Wei Yang
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=152738260746.11641.13275998345345705617.stgit@dwillia2-desk3.amr.corp.intel.com \
--to=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).