Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757292Ab0GUS0J (ORCPT ); Wed, 21 Jul 2010 14:26:09 -0400 Received: from cassiel.sirena.org.uk ([80.68.93.111]:44696 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751845Ab0GUS0H (ORCPT ); Wed, 21 Jul 2010 14:26:07 -0400 Date: Wed, 21 Jul 2010 19:24:58 +0100 From: Mark Brown To: Micha?? Nazarewicz Cc: Daniel Walker , linux-mm@kvack.org, Marek Szyprowski , Pawel Osciak , Xiaolin Zhang , Hiremath Vaibhav , Robert Fekete , Marcus Lorentzon , linux-kernel@vger.kernel.org, Kyungmin Park , linux-arm-msm@vger.kernel.org Subject: Re: [PATCH 2/4] mm: cma: Contiguous Memory Allocator added Message-ID: <20100721182457.GE10930@sirena.org.uk> References: <1279649724.26765.23.camel@c-dwalke-linux.qualcomm.com> <20100721135229.GC10930@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: He who laughs last didn't get the joke. User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: broonie@sirena.org.uk X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1666 Lines: 33 On Wed, Jul 21, 2010 at 04:31:35PM +0200, Micha?? Nazarewicz wrote: > On Wed, 21 Jul 2010 15:52:30 +0200, Mark Brown wrote: > > If this does need to be configured per system would having platform data > > of some kind in the kernel not be a sensible a place to do it, > The current version (and the next version I'm working on) of the code > has cma_defaults() call. It is intended to be called from platform > initialisation code to provide defaults. So the command line is just a way of overriding that? That makes things a lot nicer - normally the device would use the defaults and the command line would be used in development. > > or even > > having a way of configuring this at runtime (after all, the set of > > currently active users may vary depending on the current configuration > > and keeping everything allocated all the time may be wasteful)? > I am currently working on making the whole thing more dynamic. I imagine > the list of regions would stay pretty much the same after kernel has > started (that's because one cannot reliably allocate new big contiguous > memory regions) but it will be possible to change the set of rules, etc. Yes, I think it will be much easier to be able to grab the regions at startup but hopefully the allocation within those regions can be made much more dynamic. This would render most of the configuration syntax unneeded. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/