Re: [RFC][PATCH 6/6] staging: android: ion: Introduce new ioctls for dynamic heaps

On 06/08/2016 08:34 AM, Brian Starkey wrote: Hi, I'm finding "usage_id" a bit confusing - there's not a very clear distinction between usage_id and heap ID. For instance, ION_IOC_USAGE_CNT claims to return the number of usage IDs, but seems to return the number of heaps (i.e. number heap IDs,

Re: [RFC][PATCH 6/6] staging: android: ion: Introduce new ioctls for dynamic heaps

On 06/08/2016 06:50 AM, Liviu Dudau wrote: On Mon, Jun 06, 2016 at 11:23:33AM -0700, Laura Abbott wrote: From: Laura Abbott The Ion ABI for heaps is limiting to work with for more complex systems. Heaps have to be registered at boot time with known ids available to

Re: [RFC][PATCH 6/6] staging: android: ion: Introduce new ioctls for dynamic heaps

Hi, I'm finding "usage_id" a bit confusing - there's not a very clear distinction between usage_id and heap ID. For instance, ION_IOC_USAGE_CNT claims to return the number of usage IDs, but seems to return the number of heaps (i.e. number heap IDs, some of which might be usage_ids). Similarly,

Re: [RFC][PATCH 6/6] staging: android: ion: Introduce new ioctls for dynamic heaps

On Mon, Jun 06, 2016 at 11:23:33AM -0700, Laura Abbott wrote: > From: Laura Abbott > > > The Ion ABI for heaps is limiting to work with for more complex systems. > Heaps have to be registered at boot time with known ids available to > userspace. This becomes a tight

[RFC][PATCH 6/6] staging: android: ion: Introduce new ioctls for dynamic heaps

From: Laura Abbott The Ion ABI for heaps is limiting to work with for more complex systems. Heaps have to be registered at boot time with known ids available to userspace. This becomes a tight ABI which is prone to breakage. Introduce a new mechanism for registering