From: Ashok Raj <ashok.raj@intel.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com,
ktokunag@redhat.com, akpm@osdl.org
Subject: Re: [RFC][PATCH] node hotplug : register_cpu() changes [0/3]
Date: Wed, 24 May 2006 17:36:39 -0700 [thread overview]
Message-ID: <20060524173639.A2506@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060525093418.b1639de2.kamezawa.hiroyu@jp.fujitsu.com>; from kamezawa.hiroyu@jp.fujitsu.com on Thu, May 25, 2006 at 09:34:18AM +0900
On Thu, May 25, 2006 at 09:34:18AM +0900, KAMEZAWA Hiroyuki wrote:
>
> Currently, I think creating new empty node (pgdat) at onlining can work.
> by cpu hotplug notifier chain, dangling cpus will create new pgdat.
> If people want to see node <-> cpu relationship before onlining cpu, I' ll have
> to do complicated work.
>
Iam ok with this patch, no need to get anything complicated without good
reason.
Just want to make sure assumptions for cpu only nodes are not broken, as long
as we have your implementation take care of those, this is good.
--
Cheers,
Ashok Raj
- Open Source Technology Center
prev parent reply other threads:[~2006-05-25 0:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 10:56 [RFC][PATCH] node hotplug : register_cpu() changes [0/3] KAMEZAWA Hiroyuki
2006-05-23 11:00 ` [RFC][PATCH] node hotplug [1/3] register-cpu-remove-node-struct KAMEZAWA Hiroyuki
2006-05-23 11:02 ` [RFC][PATCH] node hotplug [2/3] fixes callres of register_cpu KAMEZAWA Hiroyuki
2006-05-23 11:03 ` [RFC][PATCH] node hotplug [3/3] register_node fix KAMEZAWA Hiroyuki
2006-05-23 14:52 ` [RFC][PATCH] node hotplug : register_cpu() changes [0/3] Ashok Raj
2006-05-24 0:18 ` KAMEZAWA Hiroyuki
2006-05-24 7:05 ` KAMEZAWA Hiroyuki
2006-05-24 14:51 ` Ashok Raj
2006-05-25 0:34 ` KAMEZAWA Hiroyuki
2006-05-25 0:36 ` Ashok Raj [this message]
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=20060524173639.A2506@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=ktokunag@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.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