linux-kernel - Re: [PATCH -v7 0/35] tip related: not use bootmem for x86

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: <1266200846.16346.111.camel@pasglop>
Date:	Mon, 15 Feb 2010 13:27:26 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.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>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH -v7 0/35] tip related: not use  bootmem for x86

On Wed, 2010-02-10 at 01:20 -0800, Yinghai Lu wrote:
> 
> The reserve_early() method is list/range based and can handle vast
> amounts of not very fragmented memory - perfect for basically all the
> real bootmem purposes (which is to bootstrap the buddy).
> 
> reserve_early() allocated memory could be freed into the buddy later
> on
> as well. The main reason why bootmem is 'destroyed' during
> free-to-buddy
> is because it has excessive internal bitmaps we want to free. With a
> list/range based reserve_early() mechanism there's no such problem -
> they can linger indefinitely and there's near zero allocation
> management
> overhead. " 

Various archs use lib/lmb.c for representing physical memory and
doing early allocations. Might be something to extend ?

Cheers,
Ben.


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