From: <mike.travis@hpe.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
Andrew Banman <andrew.banman@hpe.com>,
jgross@suse.com, dan.j.williams@intel.com, mhocko@suse.com,
kirill.shutemov@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] x86/platform/UV: Update Memory Block Size Setting
Date: Thu, 24 May 2018 15:17:11 -0500 [thread overview]
Message-ID: <20180524201711.437084301@stormcage.americas.sgi.com> (raw)
Update support for the UV kernel to accommodate Intel BIOS changes in
NVDIMM alignment, which caused UV BIOS to align the memory boundaries
on different blocks than the previous UV standard of 2GB.
Background: Since 2009 the UV arch dependent support has used 2GB as the
memory block size mainly to reduce the number of physical memory blocks
when a 16TB memory capable machine was introduced. This significantly
reduced the time to initialize memory during system startup, and
has worked fine until Intel added PMEM NVDIMM's to the architecture.
This has caused the alignment boundary to be reduced to whatever is
needed to accommodate these new devices.
There are no other changes suggested by this patch set. Basically the
previous strict boundary of 2GB has been relaxed to allow the arch
dependent code to adjust this memory block size depending on the
system requirements of the running environment.
* Patch 1
Add a function for any arch dependent call to "adjust" this fixed
memory block size.
* Patch 2
Add a function to check what the minimum memory block size that can
be used to accommodate where BIOS has set the boundaries for all of
memory placement within node ranges.
* Patch 3
Add a UV specific kernel arg to adjust for other memory block size
adjustments that may be required with future new DIMM restrictions.
Note that it can be raised (to 64GB) as well as lowered. This should
allow potential testing when the number of physical address bits are
raised from the current 46 bit limit to 52 bits.
Note that an option I did consider was to make Patch 3 a more generic
function for all arches to use (IOW, with or without CONFIG_X86_UV set).
Opinions welcome about this.
--
next reply other threads:[~2018-05-24 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 20:17 mike.travis [this message]
2018-05-24 20:17 ` [PATCH 1/3] x86/platform/UV: Add adjustable set memory block size function mike.travis
2018-05-24 20:17 ` [PATCH 2/3] x86/platform/UV: Use new " mike.travis
2018-05-24 20:17 ` [PATCH 3/3] x86/platform/UV: Add kernel parameter to set memory block size mike.travis
-- strict thread matches above, loose matches on Subject: below --
2018-05-10 23:18 [PATCH 0/3] x86/platform/UV: Update Memory Block Size Setting mike.travis
2018-05-11 5:24 ` Greg KH
2018-05-11 6:48 ` Michal Hocko
2018-05-15 16:08 ` Mike Travis
2018-05-16 11:09 ` Michal Hocko
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=20180524201711.437084301@stormcage.americas.sgi.com \
--to=mike.travis@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.banman@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=russ.anderson@hpe.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
all inboxes | Powered by JetHome®