From: Robin Murphy <robin.murphy@arm.com>
To: Feng Kan <fkan@apm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, will.deacon@arm.com,
rrichter@redhat.com, herton@redhat.com
Subject: Re: [PATCH] iommu: enable bypass transaction caching for ARM SMMU 500
Date: Thu, 12 Oct 2017 13:39:39 +0100 [thread overview]
Message-ID: <d0482cb9-7af4-2a52-dde2-8d9113a4721d@arm.com> (raw)
In-Reply-To: <1507759719-16675-1-git-send-email-fkan@apm.com>
On 11/10/17 23:08, Feng Kan wrote:
> The ARM SMMU identity mapping performance was poor compared with the
> DMA mode. It was found that enable caching would restore the performance
> back to normal. The S2CRB_TLBEN bit in the ACR register would allow for
> caching of the stream to context register bypass transaction information.
I know the hardware design and reasoning behind this feature, but I'm
still a little surprised that bypass can show a measurably higher
overhead than the full DMA mapping path in practice. MMU-500 is great :D
> Signed-off-by: Feng Kan <fkan@apm.com>
> ---
> drivers/iommu/arm-smmu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index 3bdb799..b5676a8 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -59,6 +59,7 @@
> #define ARM_MMU500_ACTLR_CPRE (1 << 1)
>
> #define ARM_MMU500_ACR_CACHE_LOCK (1 << 26)
> +#define ARM_MMU500_ACR_S2CRB_TLBEN (1 << 10)
> #define ARM_MMU500_ACR_SMTNMB_TLBEN (1 << 8)
>
> #define TLB_LOOP_TIMEOUT 1000000 /* 1s! */
> @@ -1606,7 +1607,7 @@ static void arm_smmu_device_reset(struct arm_smmu_device *smmu)
> * Allow unmatched Stream IDs to allocate bypass
> * TLB entries for reduced latency.
> */
> - reg |= ARM_MMU500_ACR_SMTNMB_TLBEN;
> + reg |= ARM_MMU500_ACR_SMTNMB_TLBEN | ARM_MMU500_ACR_S2CRB_TLBEN;
> writel_relaxed(reg, gr0_base + ARM_SMMU_GR0_sACR);
> }
>
Looks correct to me, and TLB usage by bypass domains should still be
equivalent to that of translation domains, so I don't think we should
see any deleterious effects overall:
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
prev parent reply other threads:[~2017-10-12 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 22:08 Feng Kan
2017-10-12 12:39 ` Robin Murphy [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=d0482cb9-7af4-2a52-dde2-8d9113a4721d@arm.com \
--to=robin.murphy@arm.com \
--cc=fkan@apm.com \
--cc=herton@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@redhat.com \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®