Hello, On 12/08/2010 10:36 PM, David Rientjes wrote: > On Tue, 7 Dec 2010, shaohui.zheng@xxxxxxxxx wrote: > >> From: Shaohui Zheng <shaohui.zheng@xxxxxxxxx> >> >> CPU physical hot-add/hot-remove are supported on some hardwares, and it >> was already supported in current linux kernel. NUMA Hotplug Emulator provides >> a mechanism to emulate the process with software method. It can be used for >> testing or debuging purpose. >> >> CPU physical hotplug is different with logical CPU online/offline. Logical >> online/offline is controled by interface /sys/device/cpu/cpuX/online. CPU >> hotplug emulator uses probe/release interface. It becomes possible to do cpu >> hotplug automation and stress >> >> Add cpu interface probe/release under sysfs for x86_64. User can use this >> interface to emulate the cpu hot-add and hot-remove process. >> >> Directive: >> *) Reserve CPU thru grub parameter like: >> maxcpus=4 >> >> the rest CPUs will not be initiliazed. >> >> *) Probe CPU >> we can use the probe interface to hot-add new CPUs: >> echo nid > /sys/devices/system/cpu/probe >> >> *) Release a CPU >> echo cpu > /sys/devices/system/cpu/release >> >> A reserved CPU will be hot-added to the specified node. >> 1) nid == 0, the CPU will be added to the real node which the CPU >> should be in >> 2) nid != 0, add the CPU to node nid even through it is a fake node. >> > > This patch is undoubtedly going to conflict with Tejun's unification of > the 32 and 64 bit NUMA boot paths, specifically the patch at > http://marc.info/?l=linux-kernel&m=129087151912379. Oh yeah, it definitely looks like it will collide with the unification patch. The problem is more fundamental than the actual patch collisions tho. During x86_32/64 merge, some parts were left unmerged - some reflect actual differences between 32 and 64 but more were probably because it was too much work. These subtle diversions make the code unnecessarily complicated, fragile and difficult to maintain, so, in general, I think we should be heading toward unifying 32 and 64 unless the difference is caused by actual hardware even when the feature or code might not be too useful for 32bit. So, the same thing holds for NUMA hotplug emulator. 32bit supports NUMA and there already is 64bit only NUMA emulator. I think it would be much better if we take this chance to unify 32 and 64bit code paths on this area rather than going further toward the wrong direction. > Tejun, what's the status of that patchset posted on November 27? Any > comments about this change? I don't know. I pinged Ingo yesterday. Ingo? Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>