linux-kernel - Re: [PATCH 0/3] memblock related top down

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]

Date:	Tue, 28 Dec 2010 13:36:07 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Vivek Goyal <vgoyal@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [PATCH 0/3] memblock related top down

On Tue, Dec 28, 2010 at 12:21 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 12/17/2010 04:58 PM, Yinghai Lu wrote:
>> Please check
>>
>> Those three patches to make memblock allocation more top to down.
>>
>
> Please explain what you mean with "more top to down".  Not what the code
> does, but what is the goal of the patchset.

for example first node with 16g ram, it is into two parts: [0, 2g),
and [4g, 18g).

alloc_bootmem will get allocation from [0, 2g) always until we have
can not find more.

with third patch, it will try to get from [4g, 18g) at first.

second patch is need to applied before third patch, because old way
happenly get under 4g for generic bootmem under 4g

First one is trying not to put page table for [0, 4g) under 512M.

Thanks

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