lkml.org 
[lkml]   [2018]   [Feb]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] staging: android: ion: Add requested allocation alignment
From
Date
On 02/12/2018 11:11 AM, Alexey Skidanov wrote:
>
> On 02/12/2018 08:42 PM, Laura Abbott wrote:
>> On 02/10/2018 02:17 AM, Alexey Skidanov wrote:
>>> Current ion defined allocation ioctl doesn't allow to specify the
>>> requested
>>> allocation alignment. CMA heap allocates buffers aligned on buffer size
>>> page order.
>>>
>>> Sometimes, the alignment requirement is less restrictive. In such cases,
>>> providing specific alignment may reduce the external memory fragmentation
>>> and in some cases it may avoid the allocation request failure.
>>>
>> I really do not want to bring this back as part of the regular
>> ABI.
> Yes, I know it was removed in 4.12.
> Having an alignment parameter that gets used for exactly
>> one heap only leads to confusion (which is why it was removed
>> from the ABI in the first place).
> You are correct regarding the CMA heap. But, probably it may be used by
> custom heap as well.

I can think of a lot of instances where it could be used but
ultimately there needs to be an actual in kernel user who wants
it.

>> The alignment came from the behavior of the DMA APIs. Do you
>> actually need to specify any alignment from userspace or do
>> you only need page size?
> Yes. If CMA gives it for free, I would suggest to let the ion user to decide

I'm really not convinced changing the ABI yet again just to let
the user decide is actually worth it. If we can manage it, I'd
much rather see a proposal that doesn't change the ABI.

>> Thanks,
>> Laura
>>
> Thanks,
> Alexey
>

\
 
 \ /
  Last update: 2018-02-12 20:52    [W:0.055 / U:0.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site