Re: [RFC][PATCH] node hotplug : register_cpu() changes [0/3]

[KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>]

On Wed, 24 May 2006 07:51:28 -0700
Ashok Raj <ashok.raj@intel.com> wrote:

> Probably ACPI doesnt give a precise way to put the dependencies (in a certain
> order), there are EDL/EJD, but they have limitations and not directly imply
> a dependency like this. But container code having to deal with this dependency
> for add/remove is probably ok. 
> 
I know fujitsu's engineers posted codes to add devices under container in past
and it knew dependency of memory -> cpu. It was rejected.
So, the current container driver just uses acpi_bus_add/start() to add/start all
devices under the container.

> i hope container would eventually perform onlining the pieces from user space
> scripts via udev like mechanisms.
> 
> I remember folks from SGI posting patches to cpu only nodes in the past. 
> Same way there are probably IO only nodes. Are you sure we cover these cases 
> as well.

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.

I also expects we can migrate per-cpu in notifier chain if  VM-per_cpu is 
implemented.

Thanks, 
-Kame

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/