From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
hyesoo.yu@samsung.com, david@redhat.com, mhocko@suse.com,
surenb@google.com, pullip.cho@samsung.com, joaodias@google.com,
hridya@google.com, john.stultz@linaro.org,
sumit.semwal@linaro.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, hch@infradead.org,
robh+dt@kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v3 4/4] dma-buf: heaps: add chunk heap to dmabuf heaps
Date: Tue, 19 Jan 2021 07:51:51 -0800 [thread overview]
Message-ID: <YAcAF2FUhaOIDY3N@google.com> (raw)
In-Reply-To: <20210113012143.1201105-5-minchan@kernel.org>
On Tue, Jan 12, 2021 at 05:21:43PM -0800, Minchan Kim wrote:
> From: Hyesoo Yu <hyesoo.yu@samsung.com>
>
> This patch supports chunk heap that allocates the buffers that
> arranged into a list a fixed size chunks taken from CMA.
>
> The chunk heap driver is bound directly to a reserved_memory
> node by following Rob Herring's suggestion in [1].
>
> [1] https://lore.kernel.org/lkml/20191025225009.50305-2-john.stultz@linaro.org/T/#m3dc63acd33fea269a584f43bb799a876f0b2b45d
>
> Signed-off-by: Hyesoo Yu <hyesoo.yu@samsung.com>
> Signed-off-by: Hridya Valsaraju <hridya@google.com>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
DMABUF folks,
It would be great if you guys give any comments.
next prev parent reply other threads:[~2021-01-19 16:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 1:21 [PATCH v3 0/4] Chunk Heap Support on DMA-HEAP Minchan Kim
2021-01-13 1:21 ` [PATCH v3 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn Minchan Kim
2021-01-20 21:08 ` Suren Baghdasaryan
2021-01-13 1:21 ` [PATCH v3 2/4] mm: failfast mode with __GFP_NORETRY in alloc_contig_range Minchan Kim
2021-01-13 8:39 ` David Hildenbrand
2021-01-14 18:04 ` Minchan Kim
2021-01-13 1:21 ` [PATCH v3 3/4] dt-bindings: reserved-memory: Make DMA-BUF CMA heap DT-configurable Minchan Kim
2021-01-13 15:45 ` Rob Herring
2021-01-13 17:30 ` Hridya Valsaraju
2021-01-13 17:30 ` Hridya Valsaraju
2021-01-14 14:01 ` Rob Herring
2021-01-14 19:49 ` Hridya Valsaraju
2021-01-14 19:49 ` Hridya Valsaraju
2021-01-13 1:21 ` [PATCH v3 4/4] dma-buf: heaps: add chunk heap to dmabuf heaps Minchan Kim
2021-01-13 3:11 ` kernel test robot
2021-01-13 3:11 ` kernel test robot
2021-01-14 1:04 ` Minchan Kim
2021-01-14 1:04 ` Minchan Kim
2021-01-13 3:38 ` Randy Dunlap
2021-01-14 1:04 ` Minchan Kim
2021-01-13 6:25 ` kernel test robot
2021-01-13 6:25 ` kernel test robot
2021-01-19 15:51 ` Minchan Kim [this message]
2021-01-19 18:29 ` John Stultz
2021-01-19 18:29 ` John Stultz
2021-01-19 20:36 ` Minchan Kim
2021-01-19 20:36 ` Minchan Kim
2021-01-20 3:32 ` Hyesoo Yu
2021-01-20 3:32 ` Hyesoo Yu
2021-01-20 20:53 ` Suren Baghdasaryan
2021-01-20 20:53 ` Suren Baghdasaryan
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=YAcAF2FUhaOIDY3N@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=hch@infradead.org \
--cc=hridya@google.com \
--cc=hyesoo.yu@samsung.com \
--cc=joaodias@google.com \
--cc=john.stultz@linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pullip.cho@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=surenb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.