From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] drivers: dma-coherent: Introduce interface for default DMA pool
Date: Wed, 19 Jul 2017 09:20:02 +0200 [thread overview]
Message-ID: <20170719072001.GA20840@lst.de> (raw)
In-Reply-To: <1500281885-3034-2-git-send-email-vladimir.murzin@arm.com>
On Mon, Jul 17, 2017 at 09:58:04AM +0100, Vladimir Murzin wrote:
> Christoph noticed [1] that default DMA pool in current form overload
> the DMA coherent infrastructure. In reply, Robin suggested to split
> the per-device vs. global pool interfaces, so allocation/release from
> default DMA pool is driven by dma ops implementation.
>
> This patch implements Robin's idea and provide interface to
> allocate/release/mmap the default/global DMA pool.
>
> [1] https://lkml.org/lkml/2017/7/7/370
> [2] https://lkml.org/lkml/2017/7/7/431
>
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
This looks good to me. I'd just rename the existin *_from_coherent
routines to *_from_dev_coherent.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk, sza@esh.hu,
arnd@arndb.de, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, alexandre.torgue@st.com,
robin.murphy@arm.com, kbuild-all@01.org,
benjamin.gaignard@linaro.org, hch@lst.de,
m.szyprowski@samsung.com, vitaly_kuzmichev@mentor.com,
george_davis@mentor.com
Subject: Re: [RFC PATCH 1/2] drivers: dma-coherent: Introduce interface for default DMA pool
Date: Wed, 19 Jul 2017 09:20:02 +0200 [thread overview]
Message-ID: <20170719072001.GA20840@lst.de> (raw)
In-Reply-To: <1500281885-3034-2-git-send-email-vladimir.murzin@arm.com>
On Mon, Jul 17, 2017 at 09:58:04AM +0100, Vladimir Murzin wrote:
> Christoph noticed [1] that default DMA pool in current form overload
> the DMA coherent infrastructure. In reply, Robin suggested to split
> the per-device vs. global pool interfaces, so allocation/release from
> default DMA pool is driven by dma ops implementation.
>
> This patch implements Robin's idea and provide interface to
> allocate/release/mmap the default/global DMA pool.
>
> [1] https://lkml.org/lkml/2017/7/7/370
> [2] https://lkml.org/lkml/2017/7/7/431
>
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
This looks good to me. I'd just rename the existin *_from_coherent
routines to *_from_dev_coherent.
next prev parent reply other threads:[~2017-07-19 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 8:58 [RFC PATCH 0/2] Introduce interface for default DMA pool Vladimir Murzin
2017-07-17 8:58 ` Vladimir Murzin
2017-07-17 8:58 ` [RFC PATCH 1/2] drivers: dma-coherent: " Vladimir Murzin
2017-07-17 8:58 ` Vladimir Murzin
2017-07-19 7:20 ` Christoph Hellwig [this message]
2017-07-19 7:20 ` Christoph Hellwig
2017-07-17 8:58 ` [RFC PATCH 2/2] ARM: NOMMU: Wire-up default DMA interface Vladimir Murzin
2017-07-17 8:58 ` Vladimir Murzin
2017-07-19 7:21 ` Christoph Hellwig
2017-07-19 7:21 ` Christoph Hellwig
2017-07-20 9:29 ` [RFC PATCH 0/2] Introduce interface for default DMA pool Szemző András
2017-07-20 9:29 ` Szemző András
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=20170719072001.GA20840@lst.de \
--to=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.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 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.