linux-kernel - Re: [PATCH 2/3] x86: add numa_move_cpus_to

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.1.10.0905121658140.14226@qirst.com>
Date:	Tue, 12 May 2009 16:59:40 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Yinghai Lu <yinghai@...nel.org>
cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 2/3] x86: add numa_move_cpus_to_node

On Mon, 11 May 2009, Yinghai Lu wrote:

> > This going to be fun for the allocators that have put their queues on the
> > respective nodes. How are the various OS structures that were allocated on
> > the node that is downed / upped relocated?
>
> NODE_DATA is new allocated on that node is backed on line for the first time.
>
> per_cpu will still stay with old near node. because per_cpu is somehow preallocated for all possible cpu.

Slab allocators and page allocator use neither NODE_DATA nor percpu

It may be best to bring the processors down and up again if the node
assignment changes. That will cause the allocators to reallocate the per
cpu resources on the right node.

--
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/