public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Cc: dwmw2@infradead.org, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, yi.l.liu@intel.com, chao.p.peng@intel.com
Subject: Re: [PATCH v2] iommu/vt-d: Link cache tags of same iommu unit together
Date: Thu, 2 Jan 2025 11:14:32 +0800	[thread overview]
Message-ID: <7fe65fd2-40db-45bc-aa18-953e9717b685@linux.intel.com> (raw)
In-Reply-To: <20241219054358.8654-1-zhenzhong.duan@intel.com>

On 12/19/24 13:43, Zhenzhong Duan wrote:
> Cache tag invalidation requests for a domain are accumulated until a
> different iommu unit is found when traversing the cache_tags linked list.
> But cache tags of same iommu unit can be distributed in the linked list,
> this make batched flush less efficient. E.g., one device backed by iommu0
> is attached to a domain in between two devices attaching backed by iommu1.
> 
> Group cache tags together for same iommu unit in cache_tag_assign() to
> maximize the performance of batched flush.
> 
> Co-developed-by: Lu Baolu<baolu.lu@linux.intel.com>
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
> Signed-off-by: Zhenzhong Duan<zhenzhong.duan@intel.com>
> ---
> v2: avoid getting cache tag struct from list head (Baolu)
> 
>   drivers/iommu/intel/cache.c | 11 ++++++++++-
>   1 file changed, 10 insertions(+), 1 deletion(-)

Queued for v6.14. Thanks!

      reply	other threads:[~2025-01-02  3:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  5:43 [PATCH v2] iommu/vt-d: Link cache tags of same iommu unit together Zhenzhong Duan
2025-01-02  3:14 ` Baolu Lu [this message]

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=7fe65fd2-40db-45bc-aa18-953e9717b685@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=chao.p.peng@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhenzhong.duan@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