From: David Rientjes <rientjes@google.com>
To: Shaohui Zheng <shaohui.zheng@intel.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, haicheng.li@linux.intel.com,
lethal@linux-sh.org, ak@linux.intel.com,
shaohui.zheng@linux.intel.com, dave@linux.vnet.ibm.com,
gregkh@suse.de, Haicheng Li <haicheng.li@intel.com>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [7/8, v6] NUMA Hotplug Emulator: extend memory probe interface to support NUMA
Date: Wed, 1 Dec 2010 16:55:42 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1012011653530.1896@chino.kir.corp.google.com> (raw)
In-Reply-To: <20101130071437.358387592@intel.com>
On Tue, 30 Nov 2010, shaohui.zheng@intel.com wrote:
> From: Shaohui Zheng <shaohui.zheng@intel.com>
>
> Extend memory probe interface to support an extra paramter nid,
> the reserved memory can be added into this node if node exists.
>
> 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.
>
> Another format suggested by Dave Hansen:
>
> echo physical_address=0x40000000 numa_node=3 > memory/probe
>
> it is more explicit to show meaning of the parameters.
>
I don't like this interface, I think it would be much better to map the
memory region to the desired node id prior to using probe as an extention
to debugfs.
--
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-12-02 0:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 7:13 [0/8, v6] NUMA Hotplug Emulator(v6) - Introduction & Feedbacks shaohui.zheng
2010-11-30 7:13 ` [1/8, v6] NUMA Hotplug Emulator: documentation shaohui.zheng
2010-12-01 0:19 ` David Rientjes
2010-12-01 0:36 ` Shaohui Zheng
2010-11-30 7:13 ` [2/8, v6] NUMA Hotplug Emulator: Add numa=possible option shaohui.zheng
2010-12-02 1:06 ` David Rientjes
2010-12-01 23:48 ` Shaohui Zheng
2010-11-30 7:13 ` [3/8, v6] NUMA Hotplug Emulator: Add node hotplug emulation shaohui.zheng
2010-11-30 7:13 ` [4/8, v6] NUMA Hotplug Emulation: Abstract cpu register functions shaohui.zheng
2010-11-30 7:13 ` [5/8, v6] NUMA Hotplug Emulator: support cpu probe/release in x86_64 shaohui.zheng
2010-11-30 7:13 ` [6/8, v6] NUMA Hotplug Emulator: Fake CPU socket with logical CPU on x86 shaohui.zheng
2010-11-30 7:13 ` [7/8, v6] NUMA Hotplug Emulator: extend memory probe interface to support NUMA shaohui.zheng
2010-12-02 0:55 ` David Rientjes [this message]
2010-11-30 7:13 ` [8/8, v6] NUMA Hotplug Emulator: implement debugfs interface for memory probe shaohui.zheng
2010-12-02 0:57 ` David Rientjes
2010-12-01 23:45 ` Shaohui Zheng
2010-12-02 1:21 ` 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.1012011653530.1896@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@suse.de \
--cc=haicheng.li@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shaohui.zheng@intel.com \
--cc=shaohui.zheng@linux.intel.com \
/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