linux-kernel - Re: further plans on bootmem, was: Re: - bootmem-avoid-dma32-zone-by-default.patch removed from -mm tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 09 Mar 2010 23:16:35 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...xchg.org
Cc:	akpm@...ux-foundation.org, yinghai@...nel.org, x86@...nel.org,
	linux-arch@...nel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: further plans on bootmem, was: Re: -
 bootmem-avoid-dma32-zone-by-default.patch removed from -mm tree

From: Johannes Weiner <hannes@...xchg.org>
Date: Wed, 10 Mar 2010 01:01:21 +0100

> I also found it weird that it makes x86 skip an allocator level that all
> the other architectures are using, and replaces it with 'generic' code that
> nobody but x86 is using (sparc, powerpc, sh and microblaze  appear to have
> lib/lmb.c at this stage and for this purpose? lmb was also suggested by
> benh [4] but I have to admit I do not understand Yinghai's response to it).

It kind of irked me that lmb was passed over for whatever vague reason
was given.

It works fine with memory hotplug on powerpc, so a lack of hotplug
support can't be an argument for not using it.

But hey, having yet another early memory allocator instead of making
one of the existing ones do what you want, that's fine right?
--
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/