From: Robin Murphy <robin.murphy@arm.com>
To: Baolu Lu <baolu.lu@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Raj Ashok <ashok.raj@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
stable@vger.kernel.org, Sanjay Kumar <sanjay.k.kumar@intel.com>
Subject: Re: [PATCH] iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode
Date: Mon, 6 Feb 2023 11:20:44 +0000 [thread overview]
Message-ID: <4d90da14-8c08-62e1-814f-ee14fab375f8@arm.com> (raw)
In-Reply-To: <ef65f1cf-d04c-8c35-7144-d30504bf7a1c@linux.intel.com>
On 2023-02-04 06:32, Baolu Lu wrote:
> On 2023/2/4 7:04, Jacob Pan wrote:
>> Intel IOMMU driver implements IOTLB flush queue with domain selective
>> or PASID selective invalidations. In this case there's no need to track
>> IOVA page range and sync IOTLBs, which may cause significant performance
>> hit.
>
> [Add cc Robin]
>
> If I understand this patch correctly, this might be caused by below
> helper:
>
> /**
> * iommu_iotlb_gather_add_page - Gather for page-based TLB invalidation
> * @domain: IOMMU domain to be invalidated
> * @gather: TLB gather data
> * @iova: start of page to invalidate
> * @size: size of page to invalidate
> *
> * Helper for IOMMU drivers to build invalidation commands based on
> individual
> * pages, or with page size/table level hints which cannot be gathered
> if they
> * differ.
> */
> static inline void iommu_iotlb_gather_add_page(struct iommu_domain *domain,
> struct
> iommu_iotlb_gather *gather,
> unsigned long iova,
> size_t size)
> {
> /*
> * If the new page is disjoint from the current range or is
> mapped at
> * a different granularity, then sync the TLB so that the gather
> * structure can be rewritten.
> */
> if ((gather->pgsize && gather->pgsize != size) ||
> iommu_iotlb_gather_is_disjoint(gather, iova, size))
> iommu_iotlb_sync(domain, gather);
>
> gather->pgsize = size;
> iommu_iotlb_gather_add_range(gather, iova, size);
> }
>
> As the comments for iommu_iotlb_gather_is_disjoint() says,
>
> "...For many IOMMUs, flushing the IOMMU in this case is better
> than merging the two, which might lead to unnecessary invalidations.
> ..."
>
> So, perhaps the right fix for this performance issue is to add
>
> if (!gather->queued)
>
> in iommu_iotlb_gather_add_page() or iommu_iotlb_gather_is_disjoint()?
> It should benefit other arch's as well.
The iotlb_gather helpers are really just that - little tools to help
drivers with various common iotlb_gather accounting patterns. The
decision whether to bother with that accounting at all should really
come beforehand, and whether a driver supports flush queues is
orthogonal to whether it uses any particular gather helper(s) or not, so
I think the patch as-is is correct.
>> This patch adds a check to avoid IOVA gather page and IOTLB sync for
>> the lazy path.
>>
>> The performance difference on Sapphire Rapids 100Gb NIC is improved by
>> the following (as measured by iperf send):
>
> Which test case have you done? Post the real data if you have any.
>
>>
>> w/o this fix~48 Gbits/s. with this fix ~54 Gbits/s
>>
>> Cc: <stable@vger.kernel.org>
>
> Again, add a Fixes tag so that people know how far this fix should be
> back ported.
Note that the overall issue probably dates back to the initial iommu-dma
conversion, but if you think it's important enough to go back beyond
5.15 when gather->queued was introduced, that'll need a different fix.
Cheers,
Robin.
next prev parent reply other threads:[~2023-02-06 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 23:04 Jacob Pan
2023-02-04 6:32 ` Baolu Lu
2023-02-06 3:48 ` Tian, Kevin
2023-02-07 6:45 ` Baolu Lu
2023-02-07 9:18 ` Tian, Kevin
2023-02-06 11:20 ` Robin Murphy [this message]
2023-02-07 6:42 ` Baolu Lu
2023-02-06 11:05 ` Robin Murphy
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=4d90da14-8c08-62e1-814f-ee14fab375f8@arm.com \
--to=robin.murphy@arm.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjay.k.kumar@intel.com \
--cc=stable@vger.kernel.org \
--cc=yi.l.liu@intel.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®