From: tip-bot for Daniel J Blueman <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: sp@numascale.com, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, bhelgaas@google.com,
daniel@numascale.com, mingo@kernel.org
Subject: [tip:x86/mm] x86: mm: Use 2GB memory block size on large-memory x86-64 systems
Date: Tue, 4 Nov 2014 09:22:29 -0800 [thread overview]
Message-ID: <tip-bdee237c0343a5d1a6cf72c7ea68e88338b26e08@git.kernel.org> (raw)
In-Reply-To: <1415089784-28779-4-git-send-email-daniel@numascale.com>
Commit-ID: bdee237c0343a5d1a6cf72c7ea68e88338b26e08
Gitweb: http://git.kernel.org/tip/bdee237c0343a5d1a6cf72c7ea68e88338b26e08
Author: Daniel J Blueman <daniel@numascale.com>
AuthorDate: Tue, 4 Nov 2014 16:29:44 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 4 Nov 2014 18:19:27 +0100
x86: mm: Use 2GB memory block size on large-memory x86-64 systems
On large-memory x86-64 systems of 64GB or more with memory hot-plug
enabled, use a 2GB memory block size. Eg with 64GB memory, this reduces
the number of directories in /sys/devices/system/memory from 512 to 32,
making it more manageable, and reducing the creation time accordingly.
This caveat is that the memory can't be offlined (for hotplug or
otherwise) with the finer default 128MB granularity, but this is
unimportant due to the high memory densities generally used with such
large-memory systems, where eg a single DIMM is the order of 16GB.
Signed-off-by: Daniel J Blueman <daniel@numascale.com>
Cc: Steffen Persvold <sp@numascale.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Link: http://lkml.kernel.org/r/1415089784-28779-4-git-send-email-daniel@numascale.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/mm/init_64.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 4cb8763..ebca30f 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -52,7 +52,6 @@
#include <asm/numa.h>
#include <asm/cacheflush.h>
#include <asm/init.h>
-#include <asm/uv/uv.h>
#include <asm/setup.h>
#include "mm_internal.h"
@@ -1247,12 +1246,10 @@ static unsigned long probe_memory_block_size(void)
/* start from 2g */
unsigned long bz = 1UL<<31;
-#ifdef CONFIG_X86_UV
- if (is_uv_system()) {
- printk(KERN_INFO "UV: memory block size 2GB\n");
+ if (totalram_pages >= (64ULL << (30 - PAGE_SHIFT))) {
+ pr_info("Using 2GB memory block size for large-memory system\n");
return 2UL * 1024 * 1024 * 1024;
}
-#endif
/* less than 64g installed */
if ((max_pfn << PAGE_SHIFT) < (16UL << 32))
next prev parent reply other threads:[~2014-11-04 17:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 8:29 [PATCH v4 1/4] Numachip: Fix 16-bit APIC ID truncation Daniel J Blueman
2014-11-04 8:29 ` [PATCH v4 2/4] Numachip: Elide self-IPI ICR polling Daniel J Blueman
2014-11-04 17:21 ` [tip:x86/platform] x86: numachip: " tip-bot for Daniel J Blueman
2014-11-04 8:29 ` [PATCH v4 3/4] Numachip: APIC driver cleanups Daniel J Blueman
2014-11-04 17:22 ` [tip:x86/platform] x86: numachip: " tip-bot for Daniel J Blueman
2014-11-04 8:29 ` [PATCH v4 4/4] Use 2GB memory block size on large-memory x86-64 systems Daniel J Blueman
2014-11-04 17:22 ` tip-bot for Daniel J Blueman [this message]
2014-11-05 22:10 ` [tip:x86/mm] x86: mm: " Yinghai Lu
2015-08-21 18:19 ` [PATCH v4 4/4] " Luck, Tony
2015-08-21 18:38 ` Yinghai Lu
2015-08-21 20:27 ` Luck, Tony
2015-08-21 20:50 ` Yinghai Lu
2015-08-21 23:54 ` Tony Luck
2015-08-24 17:46 ` Yinghai Lu
2015-08-24 20:41 ` Tony Luck
2015-08-24 21:25 ` Yinghai Lu
2015-08-24 22:39 ` Tony Luck
2015-08-24 23:41 ` Yinghai Lu
2015-08-24 23:59 ` Yinghai Lu
[not found] ` <CA+8MBbKur4SLh-7EKhU16_ra7gbvnOARg-ZWScJWH9q1hKufZQ@mail.gmail.com>
2015-08-25 19:01 ` Yinghai Lu
2015-08-25 22:06 ` Tony Luck
2015-08-26 4:17 ` Ingo Molnar
2015-08-26 5:42 ` Yinghai Lu
2015-08-26 20:49 ` Andrew Morton
2015-08-26 21:15 ` Yinghai Lu
2014-11-04 17:21 ` [tip:x86/platform] x86: numachip: Fix 16-bit APIC ID truncation tip-bot for Daniel J Blueman
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=tip-bdee237c0343a5d1a6cf72c7ea68e88338b26e08@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bhelgaas@google.com \
--cc=daniel@numascale.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
/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