[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100722150532.GA16119@rakim.wolfsonmicro.main>
Date: Thu, 22 Jul 2010 16:05:32 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Michał Nazarewicz <m.nazarewicz@...sung.com>
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
'Daniel Walker' <dwalker@...eaurora.org>, linux-mm@...ck.org,
Pawel Osciak <p.osciak@...sung.com>,
'Xiaolin Zhang' <xiaolin.zhang@...el.com>,
'Hiremath Vaibhav' <hvaibhav@...com>,
'Robert Fekete' <robert.fekete@...ricsson.com>,
'Marcus Lorentzon' <marcus.xm.lorentzon@...ricsson.com>,
linux-kernel@...r.kernel.org,
'Kyungmin Park' <kyungmin.park@...sung.com>,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 2/4] mm: cma: Contiguous Memory Allocator added
On Thu, Jul 22, 2010 at 04:58:43PM +0200, Michał Nazarewicz wrote:
> On Thu, 22 Jul 2010 15:40:56 +0200, Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
> >Yeah, agreed though I'm not convinced we can't do it via userspace
> >(initrd would give us a chance to do stuff early) or just kernel
> >rebuilds.
> If there's any other easy way of overwriting platform's default I'm happy
> to listen. :)
Netlink or similar, for example?
> >Yes, exactly - probably you can even have a default region backed by
> >normal vmalloc() RAM which would at least be able to take a stab at
> >working by default.
> Not sure what you mean here. vmalloc() allocated buffers cannot be used
> with CMA since they are not contiguous in memory.
Sorry, thinko - I just meant allocated at runtime. It'd fail a a lot of
the time so might not be worth bothering.
--
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/
Powered by blists - more mailing lists