From: Tomasz Nowicki <tn@semihalf.com>
To: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>,
joro@8bytes.org, robin.murphy@arm.com
Cc: will.deacon@arm.com, Jayachandran.Nair@cavium.com,
ard.biesheuvel@linaro.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Ganapatrao.Kulkarni@cavium.com
Subject: Re: [PATCH V2 0/1] Optimise IOVA allocations for PCI devices
Date: Thu, 12 Oct 2017 11:40:27 +0200 [thread overview]
Message-ID: <cda4f03f-acf5-9b74-d8f1-774065bfc94e@semihalf.com> (raw)
In-Reply-To: <1505897522-9237-1-git-send-email-tomasz.nowicki@caviumnetworks.com>
Hi Joerg,
Can you please have a look and see if you are fine with this patch?
Thanks in advance,
Tomasz
On 20.09.2017 10:52, Tomasz Nowicki wrote:
> Here is my test setup where I have stareted performance measurements.
>
> ------------ PCIe ------------- TX ------------- PCIe -----
> | ThunderX2 |------| Intel XL710 | ---> | Intel XL710 |------| X86 |
> | (128 cpus) | | 40GbE | | 40GbE | -----
> ------------ ------------- -------------
>
> As the reference lets take v4.13 host, SMMUv3 off and 1-thread iperf
> taskset to one CPU. The performance results I got:
>
> SMMU off -> 100%
> SMMU on -> 0,02%
>
> I followed down the DMA mapping path and found out IOVA 32-bit space
> full so that kernel was flushing rcaches for all CPUs in (1).
> For 128 CPUs, this kills the performance. Furthermore, for my case, rcaches
> contained PFNs > 32-bit mostly so the second round of IOVA allocation failed
> as well. As the consequence IOVA had to be allocated outside of 32-bit (2)
> from scratch since all rcaches have been flushed in (1).
>
> if (dma_limit > DMA_BIT_MASK(32) && dev_is_pci(dev))
> (1)--> iova = alloc_iova_fast(iovad, iova_len, DMA_BIT_MASK(32) >> shift);
>
> if (!iova)
> (2)--> iova = alloc_iova_fast(iovad, iova_len, dma_limit >> shift);
>
> My fix simply introduces parameter for alloc_iova_fast() to decide whether
> rcache flush has to be done or not. All users follow mentioned scenario
> so they should let flush as the last chance to avoid time costly iteration
> over all CPUs.
>
> This bring my iperf performance back to 100% with SMMU on.
>
> My bad feelings regarding this solution is that machines with relatively
> small numbers of CPUs may get DAC addresses more frequently for PCI
> devices. Please let me know your thoughts.
>
> Changelog:
>
> v1 --> v2
> - add missing documentation
> - fix typo
>
> Tomasz Nowicki (1):
> iommu/iova: Make rcache flush optional on IOVA allocation failure
>
> drivers/iommu/amd_iommu.c | 5 +++--
> drivers/iommu/dma-iommu.c | 6 ++++--
> drivers/iommu/intel-iommu.c | 5 +++--
> drivers/iommu/iova.c | 11 ++++++-----
> include/linux/iova.h | 5 +++--
> 5 files changed, 19 insertions(+), 13 deletions(-)
>
next prev parent reply other threads:[~2017-10-12 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 8:52 Tomasz Nowicki
2017-09-20 8:52 ` [PATCH V2 1/1] iommu/iova: Make rcache flush optional on IOVA allocation failure Tomasz Nowicki
2017-10-12 9:40 ` Tomasz Nowicki [this message]
2017-10-12 10:04 ` [PATCH V2 0/1] Optimise IOVA allocations for PCI devices Joerg Roedel
2017-10-12 10:08 ` Tomasz Nowicki
2017-10-12 11:14 ` Robin Murphy
2017-10-12 12:18 ` Joerg Roedel
2017-10-12 9:41 ` Tomasz Nowicki
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=cda4f03f-acf5-9b74-d8f1-774065bfc94e@semihalf.com \
--to=tn@semihalf.com \
--cc=Ganapatrao.Kulkarni@cavium.com \
--cc=Jayachandran.Nair@cavium.com \
--cc=ard.biesheuvel@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=tomasz.nowicki@caviumnetworks.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®