From: Dev Jain <dev.jain@arm.com>
To: catalin.marinas@arm.com, will@kernel.org, urezki@gmail.com,
akpm@linux-foundation.org, tytso@mit.edu,
adilger.kernel@dilger.ca, cem@kernel.org
Cc: ryan.roberts@arm.com, anshuman.khandual@arm.com,
shijie@os.amperecomputing.com, yang@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npiggin@gmail.com, willy@infradead.org, david@kernel.org,
ziy@nvidia.com, Dev Jain <dev.jain@arm.com>
Subject: [RESEND RFC PATCH 0/2] Enable vmalloc huge mappings by default on arm64
Date: Fri, 12 Dec 2025 09:56:59 +0530 [thread overview]
Message-ID: <20251212042701.71993-1-dev.jain@arm.com> (raw)
In the quest for reducing TLB pressure via block mappings, enable huge
vmalloc by default on arm64 for BBML2-noabort systems which support kernel
live mapping split.
This series is an RFC, because I cannot get a performance improvement for
the usual benchmarks which we have. Currently, vmalloc follows an opt-in
approach for block mappings - the users calling vmalloc_huge() are the ones
which expect the most advantage from block mappings. Most users of
vmalloc(), kvmalloc() and kvzalloc() map a single page. After applying this
series, it is expected that a considerable number of users will produce
cont mappings, and probably none will produce PMD mappings.
I am asking for help from the community in testing - I believe that one of
the testing methods is xfstests: a lot of code uses the APIs mentioned
above. I am hoping that someone can jump in and run at least xfstests, and
probably some other tests which can take advantage of the reduced TLB
pressure from vmalloc cont mappings.
---
Patchset applies on Linus' master (d358e5254674).
Dev Jain (2):
mm/vmalloc: Do not align size to huge size
arm64/mm: Enable huge-vmalloc by default
arch/arm64/include/asm/vmalloc.h | 6 +++++
arch/arm64/mm/pageattr.c | 4 +--
include/linux/vmalloc.h | 7 ++++++
mm/vmalloc.c | 43 +++++++++++++++++++++++++-------
4 files changed, 48 insertions(+), 12 deletions(-)
--
2.30.2
next reply other threads:[~2025-12-12 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 4:26 Dev Jain [this message]
2025-12-12 4:27 ` [RESEND RFC PATCH 1/2] mm/vmalloc: Do not align size to huge size Dev Jain
2025-12-22 11:47 ` Uladzislau Rezki
2025-12-24 5:05 ` Dev Jain
2025-12-12 4:27 ` [RESEND RFC PATCH 2/2] arm64/mm: Enable huge-vmalloc by default Dev 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=20251212042701.71993-1-dev.jain@arm.com \
--to=dev.jain@arm.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cem@kernel.org \
--cc=david@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=shijie@os.amperecomputing.com \
--cc=tytso@mit.edu \
--cc=urezki@gmail.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--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;
as well as URLs for NNTP newsgroup(s).