From: Michael Ellerman <mpe@ellerman•id.au>
To: Robin Murphy <robin.murphy@arm•com>,
roy.pledge@nxp•com, oss@buserror•net,
linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org, devicetree@vger•kernel.org
Cc: madalin.bucur@nxp•com
Subject: Re: [RFC PATCH 2/5] soc/fsl/qbman: Use shared-dma-pool for QMan private memory allocations
Date: Fri, 31 Mar 2017 14:27:51 +1100 [thread overview]
Message-ID: <871ste5dmw.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <b1cd8d44-8c74-ab50-5dc9-1f978cae5bdf@arm.com>
Robin Murphy <robin.murphy@arm•com> writes:
> Hi Roy,
>
> On 29/03/17 22:13, Roy Pledge wrote:
>> Use the shared-memory-pool mechanism for frame queue descriptor and
>> packed frame descriptor record area allocations.
>
> Thanks for persevering with this - in my opinion it's now looking like
> it was worth the effort :)
>
> AFAICS the ioremap_wc() that this leads to does appear to give back
> something non-cacheable on PPC (assuming "pgprot_noncached_wc" isn't
> horrendously misnamed), and "no-map" should rule out any cacheable
> linear map alias existing, so it would seem that this approach should
> avert Scott's concerns about attribute mismatches.
How does 'no-map' translate into something being excluded from the
linear mapping?
cheers
next prev parent reply other threads:[~2017-03-31 3:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 21:13 [RFC PATCH 0/5] soc/fsl/qbman: Rework private memory allocations Roy Pledge
2017-03-29 21:13 ` [RFC PATCH 1/5] soc/fsl/qbman: Use shared-dma-pool for BMan " Roy Pledge
2017-03-29 21:13 ` [RFC PATCH 2/5] soc/fsl/qbman: Use shared-dma-pool for QMan " Roy Pledge
2017-03-30 14:09 ` Robin Murphy
2017-03-31 3:27 ` Michael Ellerman [this message]
2017-03-31 17:55 ` Robin Murphy
2017-04-01 7:25 ` Scott Wood
2017-04-03 14:52 ` Robin Murphy
2017-04-04 0:24 ` Scott Wood
2017-03-29 21:13 ` [RFC PATCH 3/5] dts: arch/powerpc: Update Freescale DTS for QBMan " Roy Pledge
2017-03-29 21:13 ` [RFC PATCH 4/5] dt-bindings: soc/fsl: Update reserved memory binding for QBMan Roy Pledge
2017-04-03 15:42 ` Rob Herring
2017-04-03 19:49 ` Roy Pledge
2017-04-04 0:32 ` Scott Wood
2017-03-29 21:13 ` [RFC PATCH 5/5] powerpc: Add HAVE_GENERIC_DMA_COHERENT options to Kconfig Roy Pledge
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=871ste5dmw.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=madalin.bucur@nxp$(echo .)com \
--cc=oss@buserror$(echo .)net \
--cc=robin.murphy@arm$(echo .)com \
--cc=roy.pledge@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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