* vmalloc huge mappings
@ 2025-08-07 4:29 Dev Jain
0 siblings, 0 replies; only message in thread
From: Dev Jain @ 2025-08-07 4:29 UTC (permalink / raw)
To: npiggin; +Cc: linuxppc-dev, LKML
Hi Nicholas,
I was looking at all the previous discussions at [1] and [2], wherein
vmalloc-huge was
switched on by default, and then had to be switched off on all arches
after an year...
a) I am wondering whether ppc supports vmalloc-huge by default right now?
It doesn't look like it since the VM_ALLOW_HUGE_VMAP flag is still there.
b) From reading all the discussions, I could only figure two problems
with vmalloc-huge - one
being the drivers operating on tail pages of a large page, thus needing
us to split the compound page,
which has been solved. The other being partial permission change. Is
there any other case I am missing,
or any other problems you speculate?
[1] https://lore.kernel.org/all/20220422060107.781512-2-npiggin@gmail.com/
[2] https://lore.kernel.org/all/20220415164413.2727220-1-song@kernel.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-08-07 4:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-08-07 4:29 vmalloc huge mappings Dev Jain
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®