All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	y-goto@jp.fujitsu.com, ktokunag@redhat.com, ashok.raj@intel.com,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC][PATCH] node hotplug : register_cpu() changes [0/3]
Date: Tue, 23 May 2006 07:52:03 -0700	[thread overview]
Message-ID: <20060523075202.A24516@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060523195636.693e00d6.kamezawa.hiroyu@jp.fujitsu.com>; from kamezawa.hiroyu@jp.fujitsu.com on Tue, May 23, 2006 at 07:56:36PM +0900

On Tue, May 23, 2006 at 07:56:36PM +0900, KAMEZAWA Hiroyuki wrote:
> I found acpi container, which describes node, could evaluate cpu before
> memory. This means cpu-hot-add occurs before memory hot add.
> 

Is it possible to process memory before cpu in container hot-add code?

> In most part, cpu-hot-add doesn't depend on node hot add.
> But register_cpu, which creates symbolic link from node to cpu, requires

Dont you need all per-cpu allocated on that node? Or is it from node0 or 
something for all hotpluggable cpus?

If node is online first, then all allocations come from that node, thought you
*want* to ensure node/mem is online before cpu is up to get that benefit.

> that node should be onlined before register_cpu().
> When a node is onlined, its pgdat should be there.

  parent reply	other threads:[~2006-05-23 14:54 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 ` Ashok Raj [this message]
2006-05-24  0:18   ` [RFC][PATCH] node hotplug : register_cpu() changes [0/3] 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

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=20060523075202.A24516@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.