[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d85ac42-9e42-ba1b-9d98-8e08a44572da@redhat.com>
Date: Mon, 13 Feb 2017 11:01:14 -0800
From: Laura Abbott <labbott@...hat.com>
To: Mark Brown <broonie@...nel.org>,
Benjamin Gaignard <benjamin.gaignard@...aro.org>
Cc: linaro-kernel@...ts.linaro.org, arnd@...db.de,
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 02/13/2017 10:18 AM, Mark Brown wrote:
> 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...
>
This is the first I've heard of anything like this. Do you have any more
details/reading?
Thanks,
Laura
Powered by blists - more mailing lists