From: Laura Abbott <labbott@redhat.com>
To: Alexey Skidanov <alexey.skidanov@intel.com>,
sumit.semwal@linaro.org, gregkh@linuxfoundation.org,
arve@android.com, tkjos@android.com, maco@android.com,
devel@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: android: ion: Add requested allocation alignment
Date: Mon, 12 Feb 2018 11:52:03 -0800 [thread overview]
Message-ID: <ed842c91-4c4c-7dc0-3957-7e2684e24e32@redhat.com> (raw)
In-Reply-To: <8284b2ba-a532-23fd-4c52-7ac556d63918@intel.com>
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
>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-02-12 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 10:17 Alexey Skidanov
2018-02-12 18:42 ` Laura Abbott
2018-02-12 19:11 ` Alexey Skidanov
2018-02-12 19:52 ` Laura Abbott [this message]
2018-02-12 20:22 ` Alexey Skidanov
2018-02-12 20:46 ` Laura Abbott
2018-02-12 21:39 ` Alexey Skidanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed842c91-4c4c-7dc0-3957-7e2684e24e32@redhat.com \
--to=labbott@redhat.com \
--cc=alexey.skidanov@intel.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=sumit.semwal@linaro.org \
--cc=tkjos@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®