From: Will Deacon <will@kernel.org>
To: Ashish Mhetre <amhetre@nvidia.com>, joro@8bytes.org
Cc: robin.murphy@arm.com, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V4] iommu/io-pgtable-arm: Optimise non-coherent unmap
Date: Fri, 23 Aug 2024 16:53:57 +0100 [thread overview]
Message-ID: <20240823155357.GC525@willie-the-truck> (raw)
In-Reply-To: <20240806105135.218089-1-amhetre@nvidia.com>
On Tue, Aug 06, 2024 at 10:51:35AM +0000, Ashish Mhetre wrote:
> The current __arm_lpae_unmap() function calls dma_sync() on individual
> PTEs after clearing them. Overall unmap performance can be improved by
> around 25% for large buffer sizes by combining the syncs for adjacent
> leaf entries.
> Optimize the unmap time by clearing all the leaf entries and issuing a
> single dma_sync() for them.
> Below is detailed analysis of average unmap latency(in us) with and
> without this optimization obtained by running dma_map_benchmark for
> different buffer sizes.
>
> UnMap Latency(us)
> Size Without With % gain with
> optimiztion optimization optimization
>
> 4KB 3 3 0
> 8KB 4 3.8 5
> 16KB 6.1 5.4 11.48
> 32KB 10.2 8.5 16.67
> 64KB 18.5 14.9 19.46
> 128KB 35 27.5 21.43
> 256KB 67.5 52.2 22.67
> 512KB 127.9 97.2 24.00
> 1MB 248.6 187.4 24.62
> 2MB 65.5 65.5 0
> 4MB 119.2 119 0.17
>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
> ---
> Changes in V2:
> - Updated the commit message to be imperative.
> - Fixed ptep at incorrect index getting cleared for non-leaf entries.
>
> Changes in V3:
> - Used loop-local variables and removed redundant function variables.
> - Added check for zero-sized dma_sync in __arm_lpae_clear_pte().
> - Merged both patches into this single patch by adding check for a
> NULL gather in __arm_lpae_unmap() itself.
>
> Changes in V4:
> - Updated the subject in commit message to correctly reflect the changes
> made in this patch.
> ---
> drivers/iommu/io-pgtable-arm.c | 31 +++++++++++++++++--------------
> 1 file changed, 17 insertions(+), 14 deletions(-)
Acked-by: Will Deacon <will@kernel.org>
Joerg, please can you pick this one up for -next?
Cheers,
Will
next prev parent reply other threads:[~2024-08-23 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 10:51 [PATCH V4] iommu/io-pgtable-arm: Optimise non-coherent unmap Ashish Mhetre
2024-08-12 4:23 ` Ashish Mhetre
2024-08-19 5:05 ` Ashish Mhetre
2024-08-23 15:53 ` Will Deacon [this message]
2024-08-26 7:11 ` Joerg Roedel
[not found] <CAF6AEGvAEgFeoaxpkNw52fkt73RFg4g8+nhdR++m0ZhVsis=mA@mail.gmail.com>
2024-09-09 15:09 ` Jason Gunthorpe
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=20240823155357.GC525@willie-the-truck \
--to=will@kernel.org \
--cc=amhetre@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robin.murphy@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