From: Sumit Semwal <sumit.semwal@linaro.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Laura Abbott <labbott@redhat.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Liam Mark <lmark@codeaurora.org>,
Pratik Patel <pratikp@codeaurora.org>,
Brian Starkey <Brian.Starkey@arm.com>,
Vincent Donnefort <Vincent.Donnefort@arm.com>,
Sudipto Paul <Sudipto.Paul@arm.com>,
"Andrew F . Davis" <afd@ti.com>,
Christoph Hellwig <hch@infradead.org>,
Chenbo Feng <fengc@google.com>,
Alistair Strachan <astrachan@google.com>,
Hridya Valsaraju <hridya@google.com>,
Hillf Danton <hdanton@sina.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v12 0/5] DMA-BUF Heaps (destaging ION)
Date: Fri, 18 Oct 2019 11:51:51 +0530 [thread overview]
Message-ID: <CAO_48GGCgtA4U1CU6KV7N2m=RrwAiKgAPYghmYwirM9RJU4YTA@mail.gmail.com> (raw)
In-Reply-To: <20191018052323.21659-1-john.stultz@linaro.org>
Hi John, Andrews,
On Fri, 18 Oct 2019 at 10:53, John Stultz <john.stultz@linaro.org> wrote:
>
> Andrew brought up a reasonable concern with the CMA heap
> enumeration in the previous patch set, and I had a few other
> minor cleanups to add, so here is yet another pass at the
> dma-buf heaps patchset Andrew and I have been working on which
> tries to destage a fair chunk of ION functionality.
Thanks much for all your hardwork in getting these patches ready. It
looks like a sane approach to me to first just add the default cma
heap and work out the selection of other heaps later on.
I will wait out this weekend for any objections from others, and if I
hear none, will merge this series on Monday.
Hope that sounds reasonable?
>
> The patchset implements per-heap devices which can be opened
> directly and then an ioctl is used to allocate a dmabuf from the
> heap.
>
> The interface is similar, but much simpler then IONs, only
> providing an ALLOC ioctl.
>
> Also, I've provided relatively simple system and cma heaps.
>
> I've booted and tested these patches with AOSP on the HiKey960
> using the kernel tree here:
> https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/dma-buf-heap
>
> And the userspace changes here:
> https://android-review.googlesource.com/c/device/linaro/hikey/+/909436
>
> Compared to ION, this patchset is missing the system-contig,
> carveout and chunk heaps, as I don't have a device that uses
> those, so I'm unable to do much useful validation there.
> Additionally we have no upstream users of chunk or carveout,
> and the system-contig has been deprecated in the common/andoid-*
> kernels, so this should be ok.
>
> I've also removed the stats accounting, since any such
> accounting should be implemented by dma-buf core or the heaps
> themselves.
>
> New in v12:
> * To address Andrew's concern about adding all CMA areas, the
> CMA heap only adds the default CMA region for now.
> * Minor cleanups and prep for loading heaps from modules
> * I have patches to add other specified CMA regions, as well as
> loading heaps from modules in my WIP tree, which I will submit
> once this set is queued, here:
> https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/dma-buf-heap-WIP
>
> thanks
> -john
<snip>
Best,
Sumit.
prev parent reply other threads:[~2019-10-18 6:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 5:23 [PATCH v12 0/5] DMA-BUF Heaps (destaging ION) John Stultz
2019-10-18 5:23 ` [PATCH v12 1/5] dma-buf: Add dma-buf heaps framework John Stultz
2019-10-18 11:18 ` Brian Starkey
2019-10-18 18:26 ` John Stultz
2019-10-21 9:35 ` Brian Starkey
2019-10-21 18:32 ` John Stultz
2019-10-18 5:23 ` [PATCH v12 2/5] dma-buf: heaps: Add heap helpers John Stultz
2019-10-18 5:23 ` [PATCH v12 3/5] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz
2019-10-18 5:23 ` [PATCH v12 4/5] dma-buf: heaps: Add CMA " John Stultz
2019-10-18 11:21 ` Brian Starkey
2019-10-18 12:03 ` Benjamin Gaignard
2019-10-18 13:54 ` Andrew F. Davis
2019-10-18 18:29 ` John Stultz
2019-10-18 5:23 ` [PATCH v12 5/5] kselftests: Add dma-heap test John Stultz
2019-10-18 6:21 ` Sumit Semwal [this message]
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='CAO_48GGCgtA4U1CU6KV7N2m=RrwAiKgAPYghmYwirM9RJU4YTA@mail.gmail.com' \
--to=sumit.semwal@linaro.org \
--cc=Brian.Starkey@arm.com \
--cc=Sudipto.Paul@arm.com \
--cc=Vincent.Donnefort@arm.com \
--cc=afd@ti.com \
--cc=astrachan@google.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengc@google.com \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=hridya@google.com \
--cc=john.stultz@linaro.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=pratikp@codeaurora.org \
/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;
as well as URLs for NNTP newsgroup(s).