linux-kernel - Re: [RFC PATCHv3 00/11] Intermix Lowmem and vmalloc

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: <52C70024.1060605@sr71.net>
Date:	Fri, 03 Jan 2014 10:23:32 -0800
From:	Dave Hansen <dave@...1.net>
To:	Laura Abbott <lauraa@...eaurora.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Kyungmin Park <kmpark@...radead.org>, linux-mm@...ck.org,
	Russell King <linux@....linux.org.uk>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCHv3 00/11] Intermix Lowmem and vmalloc

On 01/02/2014 01:53 PM, Laura Abbott wrote:
> The goal here is to allow as much lowmem to be mapped as if the block of memory
> was not reserved from the physical lowmem region. Previously, we had been
> hacking up the direct virt <-> phys translation to ignore a large region of
> memory. This did not scale for multiple holes of memory however.

How much lowmem do these holes end up eating up in practice, ballpark?
I'm curious how painful this is going to get.
--
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/