Re: [RFC simple allocator v2 0/2] Simple allocator

2017-02-14 Thread Mark Brown
On Mon, Feb 13, 2017 at 11:01:14AM -0800, Laura Abbott wrote: > On 02/13/2017 10:18 AM, Mark Brown wrote: > > 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

Re: [RFC simple allocator v2 0/2] Simple allocator

2017-02-13 Thread Laura Abbott
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

Re: [RFC simple allocator v2 0/2] Simple allocator

2017-02-13 Thread Mark Brown
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...). >

[RFC simple allocator v2 0/2] Simple allocator

2017-02-13 Thread Benjamin Gaignard
version 2: - rebase code on 4.10-rc7 - fix bug in CMA allocator - do more tests with wayland dmabuf protocol: https://git.linaro.org/people/benjamin.gaignard/simple_allocator.git The goal of this RFC is to understand if a common ioctl for specific memory regions allocations is needed/welcome.