linux-kernel - Re: [patch] slab: add memory hotplug support

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.DEB.2.00.1003021253520.18137@chino.kir.corp.google.com>
Date:	Tue, 2 Mar 2010 13:03:01 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Andi Kleen <andi@...stfloor.org>,
	Nick Piggin <npiggin@...e.de>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, haicheng.li@...el.com,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [patch] slab: add memory hotplug support

On Tue, 2 Mar 2010, Christoph Lameter wrote:

> 
> Not sure how this would sync with slab use during node bootstrap and
> shutdown. Kame-san?
> 

All the nodelist allocation and initialization is done during 
MEM_GOING_ONLINE, so there should be no use of them until that 
notification cycle is done and it has graduated to MEM_ONLINE: if there 
are, there're even bigger problems because zonelist haven't even been 
built for that pgdat yet.  I can only speculate, but since Andi's 
patchset did all this during MEM_ONLINE, where the bit is already set in 
node_states[N_HIGH_MEMORY] and is passable to kmalloc_node(), this is 
probably why additional hacks had to be added elsewhere.

Other than that, concurrent kmem_cache_create() is protected by 
cache_chain_mutex.
--
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/