From: Robin Murphy <robin.murphy@arm.com>
To: joro@8bytes.org
Cc: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
thunder.leizhen@huawei.com, lorenzo.pieralisi@arm.com,
ard.biesheuvel@linaro.org, Jonathan.Cameron@huawei.com,
nwatters@codeaurora.org, ray.jui@broadcom.com
Subject: [PATCH v2 1/4] iommu/iova: Optimise rbtree searching
Date: Fri, 21 Jul 2017 12:41:58 +0100 [thread overview]
Message-ID: <fadb9d1a7e2c046b7dfc65e4e1f90ee609c19859.1500636791.git.robin.murphy@arm.com> (raw)
In-Reply-To: <cover.1500636791.git.robin.murphy@arm.com>
From: Zhen Lei <thunder.leizhen@huawei.com>
Checking the IOVA bounds separately before deciding which direction to
continue the search (if necessary) results in redundantly comparing both
pfns twice each. GCC can already determine that the final comparison op
is redundant and optimise it down to 3 in total, but we can go one
further with a little tweak of the ordering (which makes the intent of
the code that much cleaner as a bonus).
Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Zhen Lei <thunder.leizhen@huawei.com>
[rm: rewrote commit message to clarify]
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
v2: No change
drivers/iommu/iova.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c
index 246f14c83944..8f7552dc4e04 100644
--- a/drivers/iommu/iova.c
+++ b/drivers/iommu/iova.c
@@ -289,15 +289,12 @@ private_find_iova(struct iova_domain *iovad, unsigned long pfn)
while (node) {
struct iova *iova = rb_entry(node, struct iova, node);
- /* If pfn falls within iova's range, return iova */
- if ((pfn >= iova->pfn_lo) && (pfn <= iova->pfn_hi)) {
- return iova;
- }
-
if (pfn < iova->pfn_lo)
node = node->rb_left;
- else if (pfn > iova->pfn_lo)
+ else if (pfn > iova->pfn_hi)
node = node->rb_right;
+ else
+ return iova; /* pfn falls within iova's range */
}
return NULL;
--
2.12.2.dirty
next prev parent reply other threads:[~2017-07-21 11:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 11:41 [PATCH v2 0/4] Optimise 64-bit IOVA allocations Robin Murphy
2017-07-21 11:41 ` Robin Murphy [this message]
2017-07-21 11:41 ` [PATCH v2 2/4] iommu/iova: Optimise the padding calculation Robin Murphy
2017-07-21 11:42 ` [PATCH v2 3/4] iommu/iova: Extend rbtree node caching Robin Murphy
2017-07-29 3:57 ` Nate Watterson
2017-07-31 11:42 ` Robin Murphy
2017-08-03 19:41 ` Nate Watterson
2017-08-31 9:46 ` Leizhen (ThunderTown)
2017-09-19 9:42 ` Leizhen (ThunderTown)
2017-09-19 10:07 ` Robin Murphy
2017-07-21 11:42 ` [PATCH v2 4/4] iommu/iova: Make dma_32bit_pfn implicit Robin Murphy
2017-07-26 11:08 ` [PATCH v2 0/4] Optimise 64-bit IOVA allocations Joerg Roedel
2017-07-26 11:17 ` Leizhen (ThunderTown)
2017-08-08 12:03 ` Ganapatrao Kulkarni
2017-08-09 1:42 ` Leizhen (ThunderTown)
2017-08-09 3:24 ` Ganapatrao Kulkarni
2017-08-09 4:09 ` Leizhen (ThunderTown)
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=fadb9d1a7e2c046b7dfc65e4e1f90ee609c19859.1500636791.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nwatters@codeaurora.org \
--cc=ray.jui@broadcom.com \
--cc=thunder.leizhen@huawei.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®