From: Pratyush Yadav <pratyush@kernel.org>
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: pratyush@kernel.org, graf@amazon.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pasha.tatashin@soleen.com, rppt@kernel.org
Subject: Re: [PATCH] kho: Skip zero-sized bootmem areas
Date: Wed, 04 Nov 2026 13:35:35 +0100 [thread overview]
Message-ID: <2vxz8q38lqp4.fsf@kernel.org> (raw)
In-Reply-To: <20261027074028.13042-1-cp0613@linux.alibaba.com> (Chen Pei's message of "Tue, 27 Oct 2026 15:40:25 +0800")
Hi Chen,
On Tue, Oct 27 2026, Chen Pei wrote:
>> Do you see zero sized lowmem or global scratch in practice? If yes,
>> how? What's your setup?
>
> Yes. Enabling KHO for riscv64 gave me three cases. They differ in which
> size ends up 0 and in what it costs, and all three are measured:
[...]
>
>> Note that I already fixed this for per-node areas since those do end
>> up with no allocations with movable_node set [0].
>
> That one covers the per-node loop only; lowmem and global are still
> unconditional in linux-next today, which is what cases 1, 2 and 3 above
> are about. Is there anything I have not considered here? Please point
> it out and I will follow up accordingly.
Mike sent out [0] recently which should fix this problem. Please take a
look at that, and see if it works for you.
[0] https://lore.kernel.org/kexec/20261103-kho-bootmem-sizing-v1-1-45aa74098f34@kernel.org/
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-11-04 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:18 [PATCH] kho: Skip zero-sized bootmem areas Chen Pei
2026-10-26 13:23 ` sashiko-bot
2026-10-26 14:22 ` Pratyush Yadav
2026-10-27 7:40 ` Chen Pei
2026-11-04 12:35 ` Pratyush Yadav [this message]
2026-11-04 13:39 ` Chen Pei
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=2vxz8q38lqp4.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=cp0613@linux.alibaba.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.