From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: George Guo <dongtai.guo@linux.dev>, Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
changyuanl@google.com, akpm@linux-foundation.org,
Huacai Chen <chenhuacai@kernel.org>,
Kexin Liu <liukexin@kylinos.cn>,
guodongtai@kylinos.cn, kexec@lists.infradead.org,
linux-mm@kvack.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] liveupdate: kho: calculate per-node scratch sizes before allocation
Date: Tue, 8 Sep 2026 08:35:51 +0530 [thread overview]
Message-ID: <0e8d8903-069f-413d-b96c-5c8c501fb5cf@linux.ibm.com> (raw)
In-Reply-To: <20260907102414.18958-1-dongtai.guo@linux.dev>
On 07/09/26 15:54, George Guo wrote:
> Hi Mike,
>
>> This reads as LLM-generated text. Please add LLM attribution as per
>>
>> https://docs.kernel.org/process/coding-assistants.html#attribution
> I'll add the Assisted-by tag.
>
>> Can't we just calculated all the sizes first and than do the allocations?
> Yes, I'll rework this to calculate all scratch sizes together before
> allocating the scratch areas.
>
> Adding Sourabh to Cc, since this relates to the scratch-sizing discussion
> in the PowerPC KHO thread.
>
> Sourabh, this patch prevents newly allocated scratch areas from being
> counted in the per-node baseline. It does not address the overlap between
> global and per-node accounting. Could you review this approach as well?
Sure I will review your patch.
- Sourabh Jain
next prev parent reply other threads:[~2026-09-08 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 2:51 [PATCH 1/1] liveupdate: kho: calculate per-node scratch sizes before allocation George Guo
2026-09-06 20:07 ` Mike Rapoport
2026-09-07 10:24 ` George Guo
2026-09-08 3:05 ` Sourabh Jain [this message]
2026-09-12 6:33 ` Sourabh Jain
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=0e8d8903-069f-413d-b96c-5c8c501fb5cf@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=changyuanl@google.com \
--cc=chenhuacai@kernel.org \
--cc=dongtai.guo@linux.dev \
--cc=graf@amazon.com \
--cc=guodongtai@kylinos.cn \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liukexin@kylinos.cn \
--cc=loongarch@lists.linux.dev \
--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 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.