linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Shaohui Zheng <shaohui.zheng@intel.com>
Cc: Andrew Morton <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, Greg Kroah-Hartman <gregkh@suse.de>,
	Haicheng Li <haicheng.li@intel.com>
Subject: Re: [patch 7/7, v7] NUMA Hotplug Emulator: Implement mem_hotplug/add_memory debugfs interface
Date: Thu, 2 Dec 2010 15:37:03 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1012021534140.6878@chino.kir.corp.google.com> (raw)
In-Reply-To: <20101202050737.651398415@intel.com>

On Thu, 2 Dec 2010, shaohui.zheng@intel.com wrote:

> From:  Shaohui Zheng <shaohui.zheng@intel.com>
> 
> Add mem_hotplug/add_memory interface to support to memory hotplug emulation.
> the reserved memory can be added into desired node with this interface.
> 
> Add a memory section(128M) to node 3(boots with mem=1024m)
> 
> 	echo 0x40000000,3 > mem_hotplug/add_memory
> 
> And more we make it friendly, it is possible to add memory to do
> 
> 	echo 3g > mem_hotplug/add_memory
> 	echo 1024m,3 > mem_hotplug/add_memory
> 
> Another format suggested by Dave Hansen:
> 
> 	echo physical_address=0x40000000 numa_node=3 > mem_hotplug/add_memory
> 
> it is more explicit to show meaning of the parameters.
> 

NACK, we don't need such convoluted definitions if debugfs were extended 
with per-node triggers to add_memory as I suggested in v6 of your 
proposal:

	/sys/kernel/debug/mem_hotplug/add_node (already exists)
	/sys/kernel/debug/mem_hotplug/node0/add_memory
	/sys/kernel/debug/mem_hotplug/node1/add_memory
	...

You can then write a physical starting address to the add_memory files to 
hotadd memory to a node other than the one to which it has physical 
affinity.  This is much more extendable if we add additional per-node 
triggers later.

It would also be helpful if you were to reach consensus on the matters 
under discussion before posting a new version of your patchset everyday.

--
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>

  reply	other threads:[~2010-12-02 23:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02  5:05 [patch 0/7, v7] NUMA Hotplug Emulator (v7) shaohui.zheng
2010-12-02  5:05 ` [patch 1/7, v7] NUMA Hotplug Emulator: documentation shaohui.zheng
2010-12-02  5:05 ` [patch 2/7, v7] NUMA Hotplug Emulator: Add numa=possible option shaohui.zheng
2010-12-02  5:05 ` [patch 3/7, v7] NUMA Hotplug Emulator: Add node hotplug emulation shaohui.zheng
2010-12-02  5:05 ` [patch 4/7, v7] NUMA Hotplug Emulation: Abstract cpu register functions shaohui.zheng
2010-12-02  5:05 ` [patch 5/7, v7] NUMA Hotplug Emulator: Support cpu probe/release in x86_64 shaohui.zheng
2010-12-02  5:05 ` [patch 6/7, v7] NUMA Hotplug Emulator: Fake CPU socket with logical CPU on x86 shaohui.zheng
2010-12-02  5:05 ` [patch 7/7, v7] NUMA Hotplug Emulator: Implement mem_hotplug/add_memory debugfs interface shaohui.zheng
2010-12-02 23:37   ` David Rientjes [this message]
2010-12-05 23:50     ` Shaohui Zheng

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.1012021534140.6878@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=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