linux-kernel - Re: Query about merging memblock and bootmem into one new alloc

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: <20151222094747.GA25114@ravnborg.org>
Date:	Tue, 22 Dec 2015 10:47:47 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Laura Abbott <labbott@...hat.com>,
	Sumit Gupta <sumit.g.007@...il.com>, inux-mm@...ck.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: Query about merging memblock and bootmem into one new alloc

On Mon, Dec 21, 2015 at 11:01:01PM +0100, Arnd Bergmann wrote:
> On Monday 21 December 2015, Laura Abbott wrote:
> > ARM no longer uses bootmem, just memblock (see 84f452b1e8fc73ac0e31254c66e3e2260ce5263d
> > ARM: mm: Remove bootmem code and switch to NO_BOOTMEM). Any bootmem calls
> > just go to mm/nobootmem.c which is a wrapper around memblock for compatibility.
> 
> It seems the same is true on arc, arm64, powerpc, s390, sparc, tile and x86,
> and we'd ideally move all others the same way.

Small detail - sparc64 uses memblock, whereas sparc32 uses bootmem.

I know because I once tried to move sparc32 to use memblock, but
ran out of time.

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