linux-kernel - Re: [Linaro-mm-sig] [PATCH 08/10] mm: cma: Contiguous Memory Allocator added

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: <201107041645.29385.arnd@arndb.de>
Date:	Mon, 4 Jul 2011 16:45:29 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Ankita Garg <ankita@...ibm.com>
Cc:	Larry Bassel <lbassel@...eaurora.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	"'Zach Pfeffer'" <zach.pfeffer@...aro.org>,
	"'Daniel Walker'" <dwalker@...eaurora.org>,
	"'Daniel Stone'" <daniels@...labora.com>,
	"'Jesse Barker'" <jesse.barker@...aro.org>,
	"'Mel Gorman'" <mel@....ul.ie>,
	"'KAMEZAWA Hiroyuki'" <kamezawa.hiroyu@...fujitsu.com>,
	linux-kernel@...r.kernel.org,
	"'Michal Nazarewicz'" <mina86@...a86.com>,
	linaro-mm-sig@...ts.linaro.org, linux-mm@...ck.org,
	"'Kyungmin Park'" <kyungmin.park@...sung.com>,
	"'Andrew Morton'" <akpm@...ux-foundation.org>,
	linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org
Subject: Re: [Linaro-mm-sig] [PATCH 08/10] mm: cma: Contiguous Memory Allocator added

On Monday 04 July 2011, Ankita Garg wrote:
> > It still sounds to me that this can be done using the NUMA properties
> > that Linux already understands, and teaching more subsystems about it,
> > but maybe the memory hotplug developers have already come up with
> > another scheme. The way that memory hotplug and CMA choose their
> > memory regions certainly needs to take both into account. As far as
> > I can see there are both conflicting and synergistic effects when
> > you combine the two.
> > 
> 
> Recently, we proposed a generic 'memory regions' framework to exploit
> the memory power management capabilities on the embedded boards. Think
> of some of the above CMA requirements could be met by this fraemwork.
> One of the main goals of regions is to make the VM aware of the hardware
> memory boundaries, like bank. For managing memory power consumption,
> memory regions are created aligned to the hardware granularity at which
> the power can be managed (ie, the memory power consumption operations
> like on/off can be performed). If attributed are associated with each of
> these regions, some of these regions could be marked as CMA-only,
> ensuring that only movable and per-bank memory is allocated. More
> details on the design can be found here:
> 
> http://lkml.org/lkml/2011/5/27/177
> http://lkml.org/lkml/2011/6/29/202
> http://lwn.net/Articles/446493/

Thanks for the pointers, that is exactly what I was looking for.

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