linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Mark Salyzyn <salyzyn@android.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-kernel@vger.kernel.org, kernel-team@android.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Yue Hu <huyue2@yulong.com>, Mike Rapoport <rppt@linux.ibm.com>,
	Will Deacon <will@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ryohei Suzuki <ryh.szk.cmnty@gmail.com>,
	Doug Berger <opendmb@gmail.com>,
	Andrey Konovalov <andreyknvl@google.com>,
	Peng Fan <peng.fan@nxp.com>,
	linux-mm@kvack.org, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] mm: export cma alloc and release
Date: Mon, 7 Oct 2019 18:53:15 +0200	[thread overview]
Message-ID: <20191007165315.GA10317@lst.de> (raw)
In-Reply-To: <aa1c5b2f-fa90-4390-edc6-33b87fab5e09@android.com>

On Mon, Oct 07, 2019 at 09:50:31AM -0700, Mark Salyzyn wrote:
> On 10/5/19 1:37 AM, Christoph Hellwig wrote:
>> On Thu, Oct 03, 2019 at 09:55:28AM +0100, Catalin Marinas wrote:
>>> Aren't drivers supposed to use the DMA API for such allocations rather
>>> than invoking cma_*() directly?
>> Yes, they are.
>
> We have an engineer assigned to rewriting the ion memory driver to use 
> dma_buf interfaces. Hopefully that effort will solve the problem of 
> requiring these interfaces to be exported so that that driver (and others) 
> can be modularized.
>
> Thanks for the reviews, drop this patch from the list and we will regroup, 
> and accept that standing code in the kernel can not be modularized for the 
> moment.

How is that different from the "DMA-BUF Heaps (destaging ION)" series
floating around?


  reply	other threads:[~2019-10-07 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 21:22 [PATCH] mm: export cma alloc and release Mark Salyzyn
2019-10-03  8:55 ` Catalin Marinas
2019-10-05  8:37   ` Christoph Hellwig
2019-10-07 16:50     ` Mark Salyzyn
2019-10-07 16:53       ` Christoph Hellwig [this message]
2019-10-07 17:06         ` Mark Salyzyn

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=20191007165315.GA10317@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=huyue2@yulong.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=opendmb@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=robin.murphy@arm.com \
    --cc=rppt@linux.ibm.com \
    --cc=ryh.szk.cmnty@gmail.com \
    --cc=salyzyn@android.com \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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).