linux-kernel - Re: [rfc][patch 0/3] bootmem2: a memory block-oriented boot time allocator

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: <87r6cflsif.fsf@saeurebad.de>
Date:	Tue, 06 May 2008 10:57:12 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Ingo Molnar <mingo@...e.hu>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Yasunori Goto <y-goto@...fujitsu.com>
Subject: Re: [rfc][patch 0/3] bootmem2: a memory block-oriented boot time allocator

Hi,

Andi Kleen <andi@...stfloor.org> writes:

>> (because a PFN is not unique anymore)
>
> That doesn't make sense. If a PFN is not uniquely mapping to a single
> memory page anymore the VM and lots of other code in the kernel will
> just not work. And each memory page can be only in a single node.

I meant it is not unique to the bootmem allocator because two bitmaps
might partially represent the same page range.

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