From: "Guo, Chaohong" <chaohong.guo@intel.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: minskey guo <chaohong_guo@linux.intel.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"prarit@redhat.com" <prarit@redhat.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: RE: [PATCH] online CPU before memory failed in pcpu_alloc_pages()
Date: Tue, 25 May 2010 09:35:27 +0800 [thread overview]
Message-ID: <CF2F38D4AE21BB4CB845318E4C5ECB671E790AF3@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <1274713162.13756.209.camel@useless.americas.hpqcorp.net>
>>
>> But currently, I don't
>> >think you can use the numa_mem_id()/cpu_to_mem() interfaces for your
>> >purpose. I suppose you could change page_alloc.c to compile
>> >local_memory_node() #if defined(CONFIG_HAVE_MEMORYLESS_NODES) ||
>> >defined
>> >(CPU_HOTPLUG) and use that function to find the nearest memory. It
>> >should return a valid node after zonelists have been rebuilt.
>> >
>> >Does that make sense?
>>
>> Yes, besides, I need to find a place in hotplug path to call set_numa_mem()
>> just as you mentioned for ia64 platform. Is my understanding right ?
>
>I don't think you can use any of the "numa_mem" functions on x86[_64]
>without doing a lot more work to expose memoryless nodes. On x86_64,
>numa_mem_id() and cpu_to_mem() always return the same as numa_node_id()
>and cpu_to_node(). This is because x86_64 code hides memoryless nodes
>and reassigns all cpus to nodes with memory. Are you planning on
>changing this such that memoryless nodes remain on-line with their cpus
>associated with them? If so, go for it! If not, then you don't need
>to [can't really, I think] use set_numa_mem()/cpu_to_mem() for your
>purposes. That's why I suggested you arrange for local_memory_node() to
>be compiled for CPU_HOTPLUG and call that function directly to obtain a
>nearby node from which you can allocate memory during cpu hot plug. Or,
>I could just completely misunderstand what you propose to do with these
>percpu variables.
Got it, thank you very much for detailed explanation.
-minskey
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-05-25 1:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 6:17 minskey guo
2010-05-20 20:43 ` Andrew Morton
2010-05-21 0:55 ` Stephen Rothwell
2010-05-21 4:44 ` KAMEZAWA Hiroyuki
2010-05-21 8:22 ` minskey guo
2010-05-21 8:39 ` KAMEZAWA Hiroyuki
2010-05-21 9:12 ` minskey guo
2010-05-21 13:21 ` Lee Schermerhorn
2010-05-24 1:03 ` Guo, Chaohong
2010-05-24 14:59 ` Lee Schermerhorn
2010-05-25 1:35 ` Guo, Chaohong [this message]
2010-05-21 12:32 ` Lee Schermerhorn
2010-05-21 4:05 ` Guo, Chaohong
2010-05-21 7:29 ` Kleen, Andi
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=CF2F38D4AE21BB4CB845318E4C5ECB671E790AF3@shsmsx501.ccr.corp.intel.com \
--to=chaohong.guo@intel.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=chaohong_guo@linux.intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=prarit@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=stable@kernel.org \
--cc=tj@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