linux-kernel - Re: [0/7,v10] NUMA Hotplug Emulator (v10)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Apr 2011 11:57:48 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	"Zhang, Yang Z" <yang.z.zhang@...el.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	Haicheng Li <haicheng.li@...ux.intel.com>, lethal@...ux-sh.org,
	Andi Kleen <andi.kleen@...el.com>, dave@...ux.vnet.ibm.com,
	Greg KH <gregkh@...e.de>, Ingo Molnar <mingo@...e.hu>,
	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org,
	Yinghai Lu <yinghai@...nel.org>, Xin Li <xin.li@...el.com>
Subject: Re: [0/7,v10] NUMA Hotplug Emulator (v10)

On Thu, 31 Mar 2011, Zhang, Yang Z wrote:

> * PATCHSET INTRODUCTION
> 
> patch 1: Documentation.
> patch 2: Adds a numa=possible=<N> command line option to set an additional N nodes
>                  as being possible for memory hotplug.
> 
> patch 3: Add node hotplug emulation, introduce debugfs node/add_node interface
> 
> patch 4: Abstract cpu register functions, make these interface friend for cpu
>                  hotplug emulation
> patch 5: Support cpu probe/release in x86, it provide a software method to hot
>                  add/remove cpu with sysfs interface.
> patch 6: Fake CPU socket with logical CPU on x86, to prevent the scheduling
>                  domain to build the incorrect hierarchy.
> patch 7: Implement per-node add_memory debugfs interface
> 

I think it would probably be better to separate these into the x86 support 
(patch 2, part of 3, 4, 5, and patch 7) and the generic memory hotplug, 
cpu, and documentation (patch 1, most of 3, wiring up in 4 and 5, patch 
7).  In each changelog you can talk about the entire scope of the feature 
and what each patch is leading to, but this separation will help to get it 
merged first by the x86 maintainers and then the generic bits through the 
-mm tree.

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