From: Richard Yang <weiyang@linux.vnet.ibm.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] Optimize the resource overlap check
Date: Sat, 5 May 2012 11:47:30 +0800 [thread overview]
Message-ID: <20120505034730.GA5648@richard> (raw)
In-Reply-To: <1335425575-2023-1-git-send-email-weiyang@linux.vnet.ibm.com>
Bjorn,
How do you think of my this version?
On Thu, Apr 26, 2012 at 03:32:55PM +0800, Wei Yang wrote:
>In coalesce_windows() it tries to check whether the res1 and res2 overlap.
>This function do four comparisons, which could be done with one
>comparisons.
>
>Also make the resource_overlaps() a common function for others.
>
>Signed-Off-By: Wei Yang <weiyang@linux.vnet.ibm.com>
>---
> arch/x86/pci/acpi.c | 12 +-----------
> include/linux/ioport.h | 7 +++++++
> 2 files changed, 8 insertions(+), 11 deletions(-)
>
>diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
>index 68c3c13..fd3f541 100644
>--- a/arch/x86/pci/acpi.c
>+++ b/arch/x86/pci/acpi.c
>@@ -181,13 +181,6 @@ setup_resource(struct acpi_resource *acpi_res, void *data)
> return AE_OK;
> }
>
>-static bool resource_contains(struct resource *res, resource_size_t point)
>-{
>- if (res->start <= point && point <= res->end)
>- return true;
>- return false;
>-}
>-
> static void coalesce_windows(struct pci_root_info *info, unsigned long type)
> {
> int i, j;
>@@ -208,10 +201,7 @@ static void coalesce_windows(struct pci_root_info *info, unsigned long type)
> * our resources no longer match the ACPI _CRS, but
> * the kernel resource tree doesn't allow overlaps.
> */
>- if (resource_contains(res1, res2->start) ||
>- resource_contains(res1, res2->end) ||
>- resource_contains(res2, res1->start) ||
>- resource_contains(res2, res1->end)) {
>+ if (resource_overlaps(res1, res2)) {
> res1->start = min(res1->start, res2->start);
> res1->end = max(res1->end, res2->end);
> dev_info(&info->bridge->dev,
>diff --git a/include/linux/ioport.h b/include/linux/ioport.h
>index e9bb22c..05d2c70 100644
>--- a/include/linux/ioport.h
>+++ b/include/linux/ioport.h
>@@ -198,5 +198,12 @@ extern int
> walk_system_ram_range(unsigned long start_pfn, unsigned long nr_pages,
> void *arg, int (*func)(unsigned long, unsigned long, void *));
>
>+static inline bool resource_overlaps(struct resource *r1,
>+ struct resource *r2)
>+{
>+ return (r1->start <= r2->end && r1->end >= r2->start);
>+}
>+
>+
> #endif /* __ASSEMBLY__ */
> #endif /* _LINUX_IOPORT_H */
>--
>1.7.4.1
--
Richard Yang
Help you, Help me
next parent reply other threads:[~2012-05-05 3:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335425575-2023-1-git-send-email-weiyang@linux.vnet.ibm.com>
2012-05-05 3:47 ` Richard Yang [this message]
2012-05-07 17:01 ` [PATCH] Optimize the resource overlap check Bjorn Helgaas
2012-05-08 1:54 ` Richard Yang
[not found] <1334223550-9514-1-git-send-email-weiyang@linux.vnet.ibm.com>
2012-04-16 9:26 ` Richard Yang
2012-04-23 17:29 ` Bjorn Helgaas
2012-04-24 3:37 ` Richard Yang
[not found] <1334284128-24925-1-git-send-email-weiyang@linux.vnet.ibm.com>
2012-04-13 9:44 ` Ram Pai
2012-04-15 14:53 ` Richard Yang
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=20120505034730.GA5648@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@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).