From: Tarun Sahu <tarunsahu@google.com>
To: dmatlack@google.com, Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pratyush Yadav <pratyush@kernel.org>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, Tarun Sahu <tarunsahu@google.com>
Subject: [PATCH] memblock: use binary search to locate candidate regions
Date: Thu, 3 Sep 2026 15:59:06 +0000 [thread overview]
Message-ID: <20260903155907.1065681-1-tarunsahu@google.com> (raw)
Use binary search (memblock_bsearch_start) in memblock_add_range() and
memblock_isolate_range() to locate candidate regions instead of linearly
scanning from index 0.
Under heavy memory fragmentation (such as KHO page preservation registering
hundreds of thousands of disjoint folios), scanning from index 0 on every
insertion and isolation results in O(N^2) complexity, causing boot-time
memory retrieval to take several minutes (~268s for 393k pages).
Using binary search reduces the worst-case complexity to O(N log N)
(and O(N) for sequential appends), cutting KHO memory retrieval time
from ~268s to ~50ms.
Signed-off-by: Tarun Sahu <tarunsahu@google.com>
---
mm/memblock.c | 38 ++++++++++++++++++++++++++++++++++++--
1 file changed, 36 insertions(+), 2 deletions(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 9ce86349a29f..88940474b020 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -160,6 +160,11 @@ static __refdata struct memblock_type *memblock_memory = &memblock.memory;
i < memblock_type->cnt; \
i++, rgn = &memblock_type->regions[i])
+#define for_each_memblock_type_from(i, memblock_type, rgn, start) \
+ for (i = (start), rgn = &memblock_type->regions[i]; \
+ i < memblock_type->cnt; \
+ i++, rgn = &memblock_type->regions[i])
+
#define memblock_dbg(fmt, ...) \
do { \
if (memblock_debug) \
@@ -591,6 +596,33 @@ static void __init_memblock memblock_insert_region(struct memblock_type *type,
type->total_size += size;
}
+/**
+ * memblock_bsearch_start - Find the first region index where rend > base
+ * @type: memblock type to search
+ * @base: base physical address of the candidate range
+ *
+ * Returns the first region index that could potentially overlap @base.
+ */
+static int __init_memblock memblock_bsearch_start(struct memblock_type *type,
+ phys_addr_t base)
+{
+ int mid, low = 0;
+ int high = type->cnt;
+
+ if (type->cnt && base >= type->regions[type->cnt - 1].base +
+ type->regions[type->cnt - 1].size)
+ return type->cnt;
+
+ while (low < high) {
+ mid = (low + high) / 2;
+ if (type->regions[mid].base + type->regions[mid].size <= base)
+ low = mid + 1;
+ else
+ high = mid;
+ }
+ return low;
+}
+
/**
* memblock_add_range - add new memblock region
* @type: memblock type to add new region into
@@ -651,7 +683,8 @@ static int __init_memblock memblock_add_range(struct memblock_type *type,
base = obase;
nr_new = 0;
- for_each_memblock_type(idx, type, rgn) {
+ for_each_memblock_type_from(idx, type, rgn,
+ memblock_bsearch_start(type, base)) {
phys_addr_t rbase = rgn->base;
phys_addr_t rend = rbase + rgn->size;
@@ -827,7 +860,8 @@ static int __init_memblock memblock_isolate_range(struct memblock_type *type,
if (memblock_double_array(type, base, size) < 0)
return -ENOMEM;
- for_each_memblock_type(idx, type, rgn) {
+ for_each_memblock_type_from(idx, type, rgn,
+ memblock_bsearch_start(type, base)) {
phys_addr_t rbase = rgn->base;
phys_addr_t rend = rbase + rgn->size;
--
2.55.0.970.g62bdec98f9-goog
next reply other threads:[~2026-09-03 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 15:59 Tarun Sahu [this message]
2026-09-03 16:17 ` [PATCH] memblock: use binary search to locate candidate regions Dev Jain
2026-09-04 15:33 ` tarunsahu
2026-09-03 18:57 ` Dongli Zhang
2026-09-04 14:51 ` tarunsahu
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=20260903155907.1065681-1-tarunsahu@google.com \
--to=tarunsahu@google.com \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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