public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for David Rientjes <rientjes@google.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	tglx@linutronix.de, hpa@linux.intel.com, rientjes@google.com
Subject: [tip:x86/numa] x86, numa: Reduce minimum fake node size to 32M
Date: Wed, 22 Dec 2010 00:57:47 GMT	[thread overview]
Message-ID: <tip-1eafd60a580e5df8ea1dc380cf71c49d6a82d667@git.kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1012011734060.1040@chino.kir.corp.google.com>

Commit-ID:  1eafd60a580e5df8ea1dc380cf71c49d6a82d667
Gitweb:     http://git.kernel.org/tip/1eafd60a580e5df8ea1dc380cf71c49d6a82d667
Author:     David Rientjes <rientjes@google.com>
AuthorDate: Wed, 1 Dec 2010 17:36:14 -0800
Committer:  H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Tue, 21 Dec 2010 16:08:47 -0800

x86, numa: Reduce minimum fake node size to 32M

This patch changes the minimum fake node size from 64MB to 32MB so it is
possible to test NUMA code at a greater scale on smaller machines
(64 nodes on a 2G machine, 1024 nodes on 32G machine with
CONFIG_NODES_SHIFT=10).

Signed-off-by: David Rientjes <rientjes@google.com>
LKML-Reference: <alpine.DEB.2.00.1012011734060.1040@chino.kir.corp.google.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
 arch/x86/include/asm/numa_64.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/include/asm/numa_64.h b/arch/x86/include/asm/numa_64.h
index 823e070..5ae8728 100644
--- a/arch/x86/include/asm/numa_64.h
+++ b/arch/x86/include/asm/numa_64.h
@@ -38,7 +38,7 @@ extern void __cpuinit numa_add_cpu(int cpu);
 extern void __cpuinit numa_remove_cpu(int cpu);
 
 #ifdef CONFIG_NUMA_EMU
-#define FAKE_NODE_MIN_SIZE	((u64)64 << 20)
+#define FAKE_NODE_MIN_SIZE	((u64)32 << 20)
 #define FAKE_NODE_MIN_HASH_MASK	(~(FAKE_NODE_MIN_SIZE - 1UL))
 #endif /* CONFIG_NUMA_EMU */
 #else

  parent reply	other threads:[~2010-12-22  0:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02  1:36 [patch 1/5] x86: reduce minimum fake node size to 32M David Rientjes
2010-12-02  1:36 ` [patch 2/5] x86: avoid compiling NUMA emulation functions without CONFIG_NUMA_EMU David Rientjes
2010-12-22  0:58   ` [tip:x86/numa] x86, numa: Avoid " tip-bot for David Rientjes
2010-12-02  1:36 ` [patch 3/5] x86: fake apicid and pxm mappings for NUMA emulation David Rientjes
2010-12-22  0:58   ` [tip:x86/numa] x86, numa: Fake " tip-bot for David Rientjes
2010-12-02  1:36 ` [patch 4/5] x86: fake node-to-cpumask " David Rientjes
2010-12-22  0:58   ` [tip:x86/numa] x86, numa: Fake " tip-bot for David Rientjes
2010-12-02  1:36 ` [patch 5/5] x86: fix cpu to node mapping for sparse node ids David Rientjes
2010-12-22  0:59   ` [tip:x86/numa] x86, numa: Fix " tip-bot for David Rientjes
2010-12-22  0:57 ` tip-bot for David Rientjes [this message]
     [not found] <alpine.DEB.2.00.1012221700590.3701@chino.kir.corp.google.com>
2010-12-24  1:36 ` [tip:x86/numa] x86, numa: Reduce minimum fake node size to 32M tip-bot for David Rientjes

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-1eafd60a580e5df8ea1dc380cf71c49d6a82d667@git.kernel.org \
    --to=rientjes@google.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.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