From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons.
Date: Mon, 9 Jun 2014 10:27:26 +0100 [thread overview]
Message-ID: <20140609092725.GB25590@arm.com> (raw)
In-Reply-To: <539262FA.8010301@codeaurora.org>
On Sat, Jun 07, 2014 at 01:55:22AM +0100, Laura Abbott wrote:
> On 6/5/2014 10:05 AM, Catalin Marinas wrote:
> > On Mon, Jun 02, 2014 at 09:03:52PM +0100, Laura Abbott wrote:
> >> Neither CMA nor noncoherent allocations support atomic allocations.
> >> Add a dedicated atomic pool to support this.
> >
> > CMA indeed doesn't support atomic allocations but swiotlb does, the only
> > problem being the vmap() to create a non-cacheable mapping. Could we not
> > use the atomic pool only for non-coherent allocations?
>
> CMA needs the atomic pool for both non-coherent and coherent allocations.
> Perhaps I should update the code so we only create the coherent atomic
> pool if CMA is used.
It's also needed with non-coherent swiotlb because of vmap (but coherent
is fine).
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: David Riley <davidriley@chromium.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ritesh Harjani <ritesh.harjani@gmail.com>
Subject: Re: [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons.
Date: Mon, 9 Jun 2014 10:27:26 +0100 [thread overview]
Message-ID: <20140609092725.GB25590@arm.com> (raw)
In-Reply-To: <539262FA.8010301@codeaurora.org>
On Sat, Jun 07, 2014 at 01:55:22AM +0100, Laura Abbott wrote:
> On 6/5/2014 10:05 AM, Catalin Marinas wrote:
> > On Mon, Jun 02, 2014 at 09:03:52PM +0100, Laura Abbott wrote:
> >> Neither CMA nor noncoherent allocations support atomic allocations.
> >> Add a dedicated atomic pool to support this.
> >
> > CMA indeed doesn't support atomic allocations but swiotlb does, the only
> > problem being the vmap() to create a non-cacheable mapping. Could we not
> > use the atomic pool only for non-coherent allocations?
>
> CMA needs the atomic pool for both non-coherent and coherent allocations.
> Perhaps I should update the code so we only create the coherent atomic
> pool if CMA is used.
It's also needed with non-coherent swiotlb because of vmap (but coherent
is fine).
--
Catalin
next prev parent reply other threads:[~2014-06-09 9:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 20:03 [PATCHv2] arm64: Add atomic pool for non-coherent and CMA allocaitons Laura Abbott
2014-06-02 20:03 ` Laura Abbott
2014-06-03 0:23 ` David Riley
2014-06-03 0:23 ` David Riley
2014-06-03 13:28 ` Will Deacon
2014-06-03 13:28 ` Will Deacon
2014-06-04 0:30 ` Laura Abbott
2014-06-04 0:30 ` Laura Abbott
2014-06-04 17:59 ` Will Deacon
2014-06-04 17:59 ` Will Deacon
2014-06-05 17:05 ` Catalin Marinas
2014-06-05 17:05 ` Catalin Marinas
2014-06-07 0:55 ` Laura Abbott
2014-06-07 0:55 ` Laura Abbott
2014-06-09 9:27 ` Catalin Marinas [this message]
2014-06-09 9:27 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2014-06-04 16:17 Ritesh Harjani
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=20140609092725.GB25590@arm.com \
--to=catalin.marinas@arm.com \
--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.