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] iommu/vt-d: Link cache tags of same iommu unit together
Date: Wed, 18 Dec 2024 11:08:47 +0800 [thread overview]
Message-ID: <897738ba-5c1f-4d42-bf10-402d59e3f430@linux.intel.com> (raw)
In-Reply-To: <20241216033809.170366-1-zhenzhong.duan@intel.com>
On 12/16/24 11:38, 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.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> drivers/iommu/intel/cache.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/intel/cache.c b/drivers/iommu/intel/cache.c
> index e5b89f728ad3..726052a841e0 100644
> --- a/drivers/iommu/intel/cache.c
> +++ b/drivers/iommu/intel/cache.c
> @@ -48,6 +48,8 @@ static int cache_tag_assign(struct dmar_domain *domain, u16 did,
> struct intel_iommu *iommu = info->iommu;
> struct cache_tag *tag, *temp;
> unsigned long flags;
> + struct cache_tag *temp2 = list_entry(&domain->cache_tags,
> + struct cache_tag, node);
Is this valid for a list head?
>
> tag = kzalloc(sizeof(*tag), GFP_KERNEL);
> if (!tag)
> @@ -73,8 +75,15 @@ static int cache_tag_assign(struct dmar_domain *domain, u16 did,
> trace_cache_tag_assign(temp);
> return 0;
> }
> + if (temp->iommu == iommu)
> + temp2 = temp;
> }
> - list_add_tail(&tag->node, &domain->cache_tags);
> + /*
> + * Link cache tags of same iommu unit together, so consponding
> + * flush ops can be batched for iommu unit.
> + */
> + list_add(&tag->node, &temp2->node);
> +
> spin_unlock_irqrestore(&domain->cache_lock, flags);
> trace_cache_tag_assign(tag);
>
next prev parent reply other threads:[~2024-12-18 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 3:38 Zhenzhong Duan
2024-12-18 3:08 ` Baolu Lu [this message]
2024-12-18 5:22 ` Duan, Zhenzhong
2024-12-18 9:06 ` Baolu Lu
2024-12-18 9:12 ` Duan, Zhenzhong
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=897738ba-5c1f-4d42-bf10-402d59e3f430@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
all inboxes | Powered by JetHome®