linux-kernel - RE: [PATCHv8 00/12] Contiguous Memory 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 for Android: free password hash cracker in your pocket

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

Message-id: <alpine.LFD.2.00.1101121357580.25498@xanadu.home>
Date:	Wed, 12 Jan 2011 14:04:12 -0500 (EST)
From:	Nicolas Pitre <nico@...xnic.net>
To:	Marek Szyprowski <m.szyprowski@...sung.com>
Cc:	'Russell King - ARM Linux' <linux@....linux.org.uk>,
	'Kyungmin Park' <kmpark@...radead.org>,
	'Michal Nazarewicz' <m.nazarewicz@...sung.com>,
	linux-arm-kernel@...ts.infradead.org,
	'Daniel Walker' <dwalker@...eaurora.org>,
	'Johan MOSSBERG' <johan.xx.mossberg@...ricsson.com>,
	'Mel Gorman' <mel@....ul.ie>, linux-kernel@...r.kernel.org,
	'Michal Nazarewicz' <mina86@...a86.com>, linux-mm@...ck.org,
	'Ankita Garg' <ankita@...ibm.com>,
	'Andrew Morton' <akpm@...ux-foundation.org>,
	linux-media@...r.kernel.org,
	'KAMEZAWA Hiroyuki' <kamezawa.hiroyu@...fujitsu.com>
Subject: RE: [PATCHv8 00/12] Contiguous Memory Allocator

On Wed, 12 Jan 2011, Marek Szyprowski wrote:

> I understand that modifying L1 page tables is definitely not a proper way of
> handling this. It simply costs too much. But what if we consider that the DMA
> memory can be only allocated from a specific range of the system memory?
> Assuming that this range of memory is known during the boot time, it CAN be
> mapped with two-level of tables in MMU. First level mapping will stay the
> same all the time for all processes, but it would be possible to unmap the
> pages required for DMA from the second level mapping what will be visible
> from all the processes at once.

How much memory are we talking about?  What is the typical figure?

> Is there any reason why such solution won't work?

It could work indeed.

One similar solution that is already in place is to use highmem for that 
reclaimable DMA memory.  It is easy to ensure affected highmem pages are 
not mapped in kernel space.  And you can decide at boot time how many 
highmem pages you want even if the system has less that 1GB of RAM.


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