From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christoph Hellwig <hch@lst.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: use the generic dma coherent remap allocator
Date: Mon, 2 Sep 2019 13:29:33 +1000 (AEST) [thread overview]
Message-ID: <46MFv12snJz9sDQ@ozlabs.org> (raw)
In-Reply-To: <20190814132230.31874-2-hch@lst.de>
On Wed, 2019-08-14 at 13:22:30 UTC, Christoph Hellwig wrote:
> This switches to using common code for the DMA allocations, including
> potential use of the CMA allocator if configured.
>
> Switching to the generic code enables DMA allocations from atomic
> context, which is required by the DMA API documentation, and also
> adds various other minor features drivers start relying upon. It
> also makes sure we have on tested code base for all architectures
> that require uncached pte bits for coherent DMA allocations.
>
> Another advantage is that consistent memory allocations now share
> the general vmalloc pool instead of needing an explicit careout
> from it.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f2902a2fb40c589b886d21518ef8a1ee87f76b0c
cheers
prev parent reply other threads:[~2019-09-02 3:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 13:22 use the generic DMA direct remap code on powerpc Christoph Hellwig
2019-08-14 13:22 ` [PATCH] powerpc: use the generic dma coherent remap allocator Christoph Hellwig
2019-08-14 14:20 ` Christophe Leroy
2019-08-14 14:23 ` Christoph Hellwig
2019-08-14 14:21 ` Christophe Leroy
2019-08-28 6:10 ` Christoph Hellwig
2019-08-28 13:34 ` Michael Ellerman
2019-08-28 14:25 ` Christoph Hellwig
2019-08-29 9:42 ` Michael Ellerman
2019-09-02 3:29 ` Michael Ellerman [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=46MFv12snJz9sDQ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=hch@lst.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.