From: Matthew Wilcox <willy@infradead.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: inux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Nick Piggin <npiggin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tlb/hugetlb: Add framework to handle PGDIR_SIZE HugeTLB pages
Date: Wed, 13 Apr 2022 17:29:54 +0100 [thread overview]
Message-ID: <Ylb6gvRJ27BCPv1z@casper.infradead.org> (raw)
In-Reply-To: <20220413100714.509888-1-anshuman.khandual@arm.com>
On Wed, Apr 13, 2022 at 03:37:14PM +0530, Anshuman Khandual wrote:
> Change tlb_remove_huge_tlb_entry() to accommodate larger PGDIR_SIZE HugeTLB
> pages via adding a new helper tlb_flush_pgd_range(). While here also update
> struct mmu_gather as required, that is add a new member cleared_pgds.
Is this just completionist junk, or are there really CPUs that support
PGDIR sized pages? We already have support for p4d (512GB), even though
at least Intel don't support pages larger than 1GB. I think the largest
size page I've heard of is 16GB on POWER. PGDIR_SIZE would be 256TB on
x86 which just seems ludicrous to be talking about supporting.
> ---
> This applies on v5.18-rc2, some earlier context could be found here
>
> https://lore.kernel.org/all/20220406112124.GD2731@worktop.programming.kicks-ass.net/
Read it, doesn't talk about any real users of this.
prev parent reply other threads:[~2022-04-13 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 10:07 [PATCH] tlb/hugetlb: Add framework to handle PGDIR_SIZE HugeTLB pages Anshuman Khandual
2022-04-13 10:19 ` Peter Zijlstra
2022-04-13 16:29 ` Matthew Wilcox [this message]
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=Ylb6gvRJ27BCPv1z@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=inux-mm@kvack.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).