Re: memory hotplug - looking for good place for cpuset hook

Dave wrote:
> Gets it a wee bit farther from memory hotplug anyway. ;)

huh?  Where Kame suggested is just a couple lines of code and one test
below where I suggested.  How is this farther from memory hotplug, as
it still seems to be in one of the main memory hotplug routines -
add_memory()?

And why would I want to place a hook that tracks hotplug added memory
nodes 'farther from memory hotplug'?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- memory hotplug - looking for good place for cpuset hook
  - From: Paul Jackson <[email protected]>
- Re: memory hotplug - looking for good place for cpuset hook
  - From: KAMEZAWA Hiroyuki <[email protected]>
- Re: memory hotplug - looking for good place for cpuset hook
  - From: Dave Hansen <[email protected]>

Prev by Date: Re: [PATCH -mm] x86_64: Adjust the timing of initializing cyc2ns_scale.
Next by Date: Re: another NUMA build error
Previous by thread: Re: memory hotplug - looking for good place for cpuset hook
Next by thread: Re: memory hotplug - looking for good place for cpuset hook
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]