From: Matthew Wilcox <willy@infradead.org>
To: Zi Yan <ziy@nvidia.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Usama Arif <usama.arif@linux.dev>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
riel@surriel.com, Shakeel Butt <shakeel.butt@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>, Barry Song <baohua@kernel.org>,
Dev Jain <dev.jain@arm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Nico Pache <npache@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Lance Yang <lance.yang@linux.dev>,
Frank van der Linden <fvdl@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] Beyond 2MB: Why Terabyte-Scale Machines Need 1GB Transparent Huge Pages
Date: Thu, 19 Feb 2026 17:13:19 +0000 [thread overview]
Message-ID: <aZdEr32uMfTGjChl@casper.infradead.org> (raw)
In-Reply-To: <87DAD8A6-85E7-4BC9-B81A-4A842DC546E3@nvidia.com>
On Thu, Feb 19, 2026 at 11:49:27AM -0500, Zi Yan wrote:
> If HW can support multiple TLB entries translating to the same physical frame
> and allow translation priority of TLB entries, this remapping would be easy
> and we can still keep the 1GB PUD mapping. Basically, we can have 1GB TLB entry
> pointing to the 1GB folio and another 4KB TLB entry pointing to the remapped
> region and overriding the part in the original 1GB vaddr region.
Uh, do you know any hardware that supports that? Every CPU I'm familiar
with has notes suggesting that trying to do this will cause you to Have
A Very Bad Day.
next prev parent reply other threads:[~2026-02-19 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 15:53 Usama Arif
2026-02-19 16:00 ` David Hildenbrand (Arm)
2026-02-19 16:48 ` Johannes Weiner
2026-02-19 16:52 ` Zi Yan
2026-02-19 17:08 ` Johannes Weiner
2026-02-19 17:09 ` David Hildenbrand (Arm)
2026-02-19 17:09 ` David Hildenbrand (Arm)
2026-02-19 16:49 ` Zi Yan
2026-02-19 17:13 ` Matthew Wilcox [this message]
2026-02-19 17:28 ` Zi Yan
2026-02-19 19:02 ` Rik van Riel
2026-02-20 10:00 ` David Hildenbrand (Arm)
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=aZdEr32uMfTGjChl@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=fvdl@google.com \
--cc=hannes@cmpxchg.org \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=npache@redhat.com \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=usama.arif@linux.dev \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox