linux-kernel - Re: [PATCH 2/4] x86, numa: Do not adjust start/end for early_node

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] [day] [month] [year] [list]

Message-ID: <20110222103920.GY31267@htj.dyndns.org>
Date:	Tue, 22 Feb 2011 11:39:20 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	David Rientjes <rientjes@...gle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Cyrill Gorcunov <gorcunov@...il.com>
Subject: Re: [PATCH 2/4] x86, numa: Do not adjust start/end for
 early_node_mem()

On Tue, Feb 22, 2011 at 11:36:53AM +0100, Tejun Heo wrote:
> So, don't remove the DMA boundary limit.  Even if the current code
> wouldn't result in that (and the current code CAN), it is a good
> sanity check to have because you don't want memory map under 16MiB no
> matter what.

Oh, if you're genuinely concerned about machines which wouldn't be
able to allocate memory map because it doesn't have enough memory
above 16MiB, the correct thing to do is removing the boundary limit
from the fallback generic allocation, NOT from the NUMA aware
allocation.

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