From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH v2 1/2] kho: use unsigned long for nr_pages
Date: Tue, 20 Jan 2026 15:06:28 +0200 [thread overview]
Message-ID: <aW991CRBJ3QlNG2i@kernel.org> (raw)
In-Reply-To: <20260116142635.b90464ed9772c146a9842370@linux-foundation.org>
On Fri, Jan 16, 2026 at 02:26:35PM -0800, Andrew Morton wrote:
> On Fri, 16 Jan 2026 11:22:14 +0000 Pratyush Yadav <pratyush@kernel.org> wrote:
>
> > With 4k pages, a 32-bit nr_pages can span up to 16 TiB. While it is a
> > lot, there exist systems with terabytes of RAM. gup is also moving to
> > using long for nr_pages. Use unsigned long and make KHO future-proof.
>
> We can expect people to be using LTS kernel five years from now,
> perhaps much longer. Machines will be bigger then!
>
> IOW, shouldn't we backport this?
The latest LTS is 6.12 that still does not have KHO, I don't think it makes
sense to backport this to 6.18.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-01-20 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 11:22 [PATCH v2 0/2] kho: clean up page initialization logic Pratyush Yadav
2026-01-16 11:22 ` [PATCH v2 1/2] kho: use unsigned long for nr_pages Pratyush Yadav
2026-01-16 22:26 ` Andrew Morton
2026-01-20 13:06 ` Mike Rapoport [this message]
2026-01-20 13:03 ` Mike Rapoport
2026-01-22 19:08 ` Pasha Tatashin
2026-01-16 11:22 ` [PATCH v2 2/2] kho: simplify page initialization in kho_restore_page() Pratyush Yadav
2026-01-20 13:05 ` Mike Rapoport
2026-01-22 19:11 ` Pasha Tatashin
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=aW991CRBJ3QlNG2i@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--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=pratyush@kernel.org \
--cc=surenb@google.com \
/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.