From: Lin Feng <linfeng@cn.fujitsu.com>
To: akpm@linux-foundation.org, tj@kernel.org
Cc: mingo@kernel.org, yinghai@kernel.org, liwanp@linux.vnet.ibm.com,
benh@kernel.crashing.org, tangchen@cn.fujitsu.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Lin Feng <linfeng@cn.fujitsu.com>
Subject: [RFC PATCH] mm: memblock: optimize memblock_find_in_range_node() to minimize the search work
Date: Fri, 4 Jan 2013 17:24:53 +0800 [thread overview]
Message-ID: <1357291493-25773-1-git-send-email-linfeng@cn.fujitsu.com> (raw)
The memblock array is in ascending order and we traverse the memblock array in
reverse order so we can add some simple check to reduce the search work.
Tejun fix a underflow bug in 5d53cb27d8, but I think we could break there for
the same reason.
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Lin Feng <linfeng@cn.fujitsu.com>
---
mm/memblock.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 6259055..a710557 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -111,11 +111,18 @@ phys_addr_t __init_memblock memblock_find_in_range_node(phys_addr_t start,
end = max(start, end);
for_each_free_mem_range_reverse(i, nid, &this_start, &this_end, NULL) {
+ /*
+ * exclude the regions out of the candidate range, since it's
+ * likely to find a suitable range, we ignore the worst case.
+ */
+ if (this_start >= end)
+ continue;
+
this_start = clamp(this_start, start, end);
this_end = clamp(this_end, start, end);
if (this_end < size)
- continue;
+ break;
cand = round_down(this_end - size, align);
if (cand >= this_start)
--
1.7.11.7
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-01-04 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 9:24 Lin Feng [this message]
2013-01-04 15:01 ` Tejun Heo
2013-01-07 1:53 ` Lin Feng
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=1357291493-25773-1-git-send-email-linfeng@cn.fujitsu.com \
--to=linfeng@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.org \
--cc=yinghai@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