[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170213181842.tn3nf7ogrwnzje2p@sirena.org.uk>
Date: Mon, 13 Feb 2017 18:18:42 +0000
From: Mark Brown <broonie@...nel.org>
To: Benjamin Gaignard <benjamin.gaignard@...aro.org>
Cc: linaro-kernel@...ts.linaro.org, arnd@...db.de, labbott@...hat.com,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, daniel.vetter@...ll.ch,
laurent.pinchart@...asonboard.com, robdclark@...il.com,
akpm@...ux-foundation.org, hverkuil@...all.nl
Subject: Re: [RFC simple allocator v2 0/2] Simple allocator
On Mon, Feb 13, 2017 at 03:45:04PM +0100, Benjamin Gaignard wrote:
> An other question is: do we have others memory regions that could be interested
> by this new framework ? I have in mind that some title memory regions could use
> it or replace ION heaps (system, carveout, etc...).
> Maybe it only solve CMA allocation issue, in this case there is no need to create
> a new framework but only a dedicated ioctl.
The software defined networking people seemed to think they had a use
case for this as well. They're not entirely upstream of course but
still...
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists