linux-kernel - Re: [PATCH 0/2] Relax restrictions on setting CONFIG

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: <20080122121400.GB31253@elte.hu>
Date:	Tue, 22 Jan 2008 13:14:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mel Gorman <mel@....ul.ie>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, apw@...dowen.org
Subject: Re: [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86


* Mel Gorman <mel@....ul.ie> wrote:

> [...] I tested this situation on a 4-node NUMA Opteron box. It didn't 
> work very well based on a few problems.
> 
> - alloc_remap() and SPARSEMEM on HIGHMEM4G explodes [1]
> - Without SRAT, there is a build failure 
> - Enabling SRAT requires BOOT_IOREMAP and it explodes early in boot
> 
> I have one fix for items 1 and 2 with the patch below. It probably 
> should be split in two but lets see if we want to pursue alternative 
> fixes to this problem first. In particular, this patch stops SPARSEMEM 
> using alloc_remap() because not enough memory is set aside. An 
> alternative solution may be to reserve more for alloc_remap() when 
> SPARSEMEM is in use.
> 
> With the patch applied, an x86-64 capable NUMA Opteron box will boot a 
> 32 bit NUMA enabled kernel with DISCONTIGMEM or SPARSEMEM. Due to the 
> lack of SRAT parsing, there is only node 0 of course.
> 
> Based on this, I have no doubt there is going to be a series of broken 
> boots while stuff like this gets rattled out. For the moment, NUMA on 
> x86 32-bit should remain CONFIG_EXPERIMENTAL.

thanks, applied.

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