public inbox for patches@lists.linux.dev
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
	iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>
Cc: patches@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] iommupt: Optimize the gather processing for DMA-FQ mode
Date: Tue, 3 Mar 2026 11:55:33 +0800	[thread overview]
Message-ID: <d1a49e84-9829-41ef-88df-c7f7a30aa2ae@linux.intel.com> (raw)
In-Reply-To: <0-v1-37d146e56632+ce4-iommupt_no_gaps_fq_jgg@nvidia.com>

On 2/27/26 23:27, Jason Gunthorpe wrote:
> In PT_FEAT_FLUSH_RANGE mode the gather was accumulated but never flushed
> and then the accumulated range was discarded by the dma-iommu code in
> DMA-FQ mode. This is basically optimal.
> 
> However for PT_FEAT_FLUSH_RANGE_NO_GAPS the page table would push flushes
> that are redundant with the flush all generated by the DMA-FQ mode.
> 
> Disable all range accumulation in the gather, and iommu_pt triggered
> flushing when in iommu_iotlb_gather_queued() indicates it is in DMA-FQ
> mode.
> 
> Reported-by: Robin Murphy<robin.murphy@arm.com>
> Closes:https://lore.kernel.org/r/794b6121-b66b-4819-b291-9761ed21cd83@arm.com
> Signed-off-by: Jason Gunthorpe<jgg@nvidia.com>
> ---
>   drivers/iommu/generic_pt/iommu_pt.h | 27 +++++++++++++++++++--------
>   1 file changed, 19 insertions(+), 8 deletions(-)

Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>

  parent reply	other threads:[~2026-03-03  3:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 15:27 [PATCH] iommupt: Optimize the gather processing for DMA-FQ mode Jason Gunthorpe
2026-02-27 21:02 ` Samiullah Khawaja
2026-03-03  3:55 ` Baolu Lu [this message]
2026-03-17 12:15 ` Joerg Roedel

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=d1a49e84-9829-41ef-88df-c7f7a30aa2ae@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=patches@lists.linux.dev \
    --cc=robin.murphy@arm.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