public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: "Francois Dugast" <francois.dugast@intel.com>,
	iommu@lists.linux.dev, intel-xe@lists.freedesktop.org,
	"Joerg Roedel" <joerg.roedel@amd.com>,
	"Calvin Owens" <calvin@wbinvd.org>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Will Deacon" <will@kernel.org>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Samiullah Khawaja" <skhawaja@google.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Tina Zhang" <tina.zhang@intel.com>,
	"Lu Baolu" <baolu.lu@linux.intel.com>,
	"Kevin Tian" <kevin.tian@intel.com>
Subject: Re: Xe performance regression with recent IOMMU changes
Date: Thu, 22 Jan 2026 09:31:31 -0400	[thread overview]
Message-ID: <20260122133131.GL1134360@nvidia.com> (raw)
In-Reply-To: <aXHAcibp/4pUB8f0@lstrano-desk.jf.intel.com>

On Wed, Jan 21, 2026 at 10:15:14PM -0800, Matthew Brost wrote:
> > > I posted some more optimizations for these cases, it should reduce the
> > > numbers.
> 
> We can try those — link? I believe I know the series, but just to make
> sure we’re on the same page.

https://patch.msgid.link/r/0-v2-973a6bdc820f+693-iommpt_map_direct_jgg@nvidia.com

I also need the answer if this testing is running on the non-cache
coherent iommu HW Intel sometimes has, it makes a difference.

I also have in mind a fairly small change to make this special unmap
case speed up.

IMHO those two together will likely get you back to close enough.

And then do link if you actually care about this scenario.

> This was a fairly common pattern prior to Leon’s series, I believe. The
> cross-references show this pattern appearing frequently in the kernel
> [1].

Yes the pattern is common but virtually nobody actually uses it with
the iommu turned on because it is something like 10x slower than using
just identity mode.

I understand this is a test suite and it should test with iommu
enabled, but I'm deeply skeptical this represents actual users who
also care about performace. If they did they'd already have set the
iommu to identity.

> > The optimizations I posted will help this noticably.
> 
> I think we need to start with a revert and then discuss whether your
> subsequent changes actually fix the problem.

We haven't even done some basic investigation, immediately demanding a
revert of such a large amount of work for a use case I suspect doesn't
have users it not reasonable.

This work was not done for no reason and is bringing performance wins
for other use cases that do actually have real users. If we eventually
really can't fix it then you can talk about reverts, but given link
will absolutely fix xe, I don't see that happening.

Try the patches, give me the new numbers, tell me if you have the
non-cache iommu and I will give you another one to try.

Jason

  parent reply	other threads:[~2026-01-22 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 13:02 Xe performance regression with recent IOMMU changes Francois Dugast
2026-01-21 13:11 ` Jason Gunthorpe
2026-01-21 18:04   ` Jason Gunthorpe
2026-01-22  6:15     ` Matthew Brost
2026-01-22  7:29       ` Leon Romanovsky
2026-01-22  7:36         ` Matthew Brost
2026-01-22 10:26           ` Leon Romanovsky
2026-01-22 13:31       ` Jason Gunthorpe [this message]
2026-01-23 16:27         ` Francois Dugast
2026-01-23 19:07           ` 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=20260122133131.GL1134360@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=calvin@wbinvd.org \
    --cc=dwmw2@infradead.org \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=joerg.roedel@amd.com \
    --cc=kevin.tian@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=robin.murphy@arm.com \
    --cc=skhawaja@google.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tina.zhang@intel.com \
    --cc=will@kernel.org \
    /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