From: David Rientjes <rientjes@google.com>
To: Shaohui Zheng <shaohui.zheng@intel.com>
Cc: akpm@linux-foundation.org, gregkh@suse.de, mingo@redhat.com,
hpa@zytor.com, tglx@linutronix.de, lethal@linux-sh.org,
ak@linux.intel.com, yinghai@kernel.org, randy.dunlap@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
haicheng.li@intel.com, haicheng.li@linux.intel.com,
shaohui.zheng@linux.intel.com
Subject: Re: [patch 2/2] mm: add node hotplug emulation
Date: Sat, 27 Nov 2010 18:00:15 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1011271754260.3764@chino.kir.corp.google.com> (raw)
In-Reply-To: <20101122014706.GB9081@shaohui>
On Mon, 22 Nov 2010, Shaohui Zheng wrote:
> > and then creating a new 128M node at runtime:
> >
> > # echo 128M@0x80000000 > /sys/devices/system/memory/add_node
> > On node 1 totalpages: 0
> > init_memory_mapping: 0000000080000000-0000000088000000
> > 0080000000 - 0088000000 page 2M
>
> For cpu/memory physical hotplug, we have the unique interface probe/release,
> it is the _standard_ interface, it is not only for x86, ppc use the the interface
> as well. For node hotplug, it should follow the rule.
>
> You are creating a new interface /sys/devices/system/memory/add_node to add both
> memory and node, you are just trying to create DUPLICATED feature with the
> memory probe interface, it breaks the rule.
>
It's not duplicated, the function of add_node is distinct since it maps
the added memory to a node that wasn't previously defined (for the x86
case, defined by the SRAT). I think this is better than an additional
abstraction layer that remaps memory to nodes above what the BIOS has
defined, and there's nothing architecture specific about add_node; if an
arch can do probe then it can use this new interface.
> I did NOT see the feature difference with our emulator patch http://lkml.org/lkml/2010/11/16/740,
> you pick up a piece of feature from emulator, and create an other thread. You
> are trying to replace the interface with a new one, which is not recommended.
> the memory probe interface is already powerful and flexible enough after apply
> our patch. What's more important, it keeps the old directives, and it maintains
> backwards compatibility.
>
This achieves the same goal in a much cleaner and generic way. It doesn't
replace anything that currently sits in the kernel, instead it competes
directly with your model for node hotplug emulation.
> Add a memory section(128M) to node 3(boots with mem=1024m)
>
> echo 0x40000000,3 > memory/probe
>
> And more we make it friendly, it is possible to add memory to do
>
> echo 3g > memory/probe
> echo 1024m,3 > memory/probe
>
> It maintains backwards compatibility.
>
My patch doesn't break backwards compatibility, it adds a new debugfs file
that allows you to test node hotplug.
> Another format suggested by Dave Hansen:
>
> echo physical_address=0x40000000 numa_node=3 > memory/probe
>
> we should not need duplicated interface /sys/devices/system/memory/add_node here.
>
We don't need to define a node id, we only need to ensure that a possible
node is not yet online and use it; we don't gain anything by trying to
hotplug node ids in a sparse or interleaved way (although it is certainly
possible with a combination of my patch and CONFIG_MEMORY_HOTREMOVE).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-28 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A24AE1FFE7AEC5489F83450EE98351BF28723FC4A7@shsmsx502.ccr.corp.intel.com>
2010-11-22 1:47 ` Shaohui Zheng
2010-11-24 6:45 ` Shaohui Zheng
2010-11-28 2:01 ` David Rientjes
2010-11-28 2:00 ` David Rientjes [this message]
2010-11-17 2:07 [0/8,v3] NUMA Hotplug Emulator - Introduction & Feedbacks shaohui.zheng
2010-11-17 2:08 ` [2/8,v3] NUMA Hotplug Emulator: infrastructure of NUMA hotplug emulation shaohui.zheng
2010-11-17 8:16 ` David Rientjes
2010-11-17 7:51 ` Shaohui Zheng
2010-11-17 21:10 ` David Rientjes
2010-11-18 4:14 ` Shaohui Zheng
2010-11-18 6:27 ` Paul Mundt
2010-11-18 5:27 ` Shaohui Zheng
2010-11-18 21:24 ` David Rientjes
2010-11-19 0:32 ` Shaohui Zheng
2010-11-21 0:48 ` David Rientjes
2010-11-21 2:28 ` [patch 1/2] x86: add numa=possible command line option David Rientjes
2010-11-21 2:28 ` [patch 2/2] mm: add node hotplug emulation David Rientjes
2010-11-21 17:34 ` Greg KH
2010-11-21 21:48 ` 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=alpine.DEB.2.00.1011271754260.3764@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=haicheng.li@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=shaohui.zheng@intel.com \
--cc=shaohui.zheng@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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