From: Cong Wang <xiyou.wangcong@gmail.com>
To: iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, joro@8bytes.org,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: [Patch v2 3/3] iommu: avoid taking iova_rbtree_lock twice
Date: Thu, 28 Nov 2019 16:48:55 -0800 [thread overview]
Message-ID: <20191129004855.18506-4-xiyou.wangcong@gmail.com> (raw)
In-Reply-To: <20191129004855.18506-1-xiyou.wangcong@gmail.com>
Both find_iova() and __free_iova() take iova_rbtree_lock,
there is no reason to take and release it twice inside
free_iova().
Fold them into the critical section by calling the unlock
versions instead.
Cc: Joerg Roedel <joro@8bytes.org>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
---
drivers/iommu/iova.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c
index 184d4c0e20b5..f46f8f794678 100644
--- a/drivers/iommu/iova.c
+++ b/drivers/iommu/iova.c
@@ -390,10 +390,14 @@ EXPORT_SYMBOL_GPL(__free_iova);
void
free_iova(struct iova_domain *iovad, unsigned long pfn)
{
- struct iova *iova = find_iova(iovad, pfn);
+ unsigned long flags;
+ struct iova *iova;
+ spin_lock_irqsave(&iovad->iova_rbtree_lock, flags);
+ iova = private_find_iova(iovad, pfn);
if (iova)
- __free_iova(iovad, iova);
+ private_free_iova(iovad, iova);
+ spin_unlock_irqrestore(&iovad->iova_rbtree_lock, flags);
}
EXPORT_SYMBOL_GPL(free_iova);
--
2.21.0
next prev parent reply other threads:[~2019-11-29 0:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 0:48 [Patch v2 0/3] iommu: reduce spinlock contention on fast path Cong Wang
2019-11-29 0:48 ` [Patch v2 1/3] iommu: match the original algorithm Cong Wang
2019-11-29 14:43 ` John Garry
2019-11-30 5:58 ` Cong Wang
2019-12-02 10:55 ` John Garry
2019-12-03 19:26 ` Cong Wang
2019-12-02 16:58 ` Christoph Hellwig
2019-12-03 19:24 ` Cong Wang
2019-11-29 0:48 ` [Patch v2 2/3] iommu: optimize iova_magazine_free_pfns() Cong Wang
2019-11-29 13:24 ` John Garry
2019-11-30 6:02 ` Cong Wang
2019-12-02 10:02 ` John Garry
2019-12-03 19:40 ` Cong Wang
2019-12-02 16:59 ` Christoph Hellwig
2019-12-03 19:28 ` Cong Wang
2019-11-29 0:48 ` Cong Wang [this message]
2019-11-29 13:34 ` [Patch v2 3/3] iommu: avoid taking iova_rbtree_lock twice John Garry
2019-11-30 6:03 ` Cong Wang
2019-12-17 9:43 ` [Patch v2 0/3] iommu: reduce spinlock contention on fast path Joerg Roedel
2019-12-18 4:32 ` Cong Wang
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=20191129004855.18506-4-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).