Letting userspace know the page size was IMO a design mistake.
Imagine a world where the page size is secret to userspace. Anything that needs page size alignment will be chosen by the kernel.
That in turn allows mixed page size, variable page size, heirarchical pages, etc.
Dylan16807•1h ago
It's hard to hide all the details, especially when you involve varied permissions over different chunks of memory.
duskwuff•1h ago
It's unavoidable. APIs like mprotect() operate on pages; there's no way to hide that from them.
viraptor•45m ago
Also various performance characteristics graphs will have steps around the multiples of page sizes. People would find out anyway. (Although maybe the runtime detection is not a bad idea)
Wowfunhappy•1h ago
So, do 4 KB page size apps work on these 16 KB page size phones? There are plenty of legacy apps (especially games I'd imagine) that will never updated for one reason or another. I would want to know if I was buying a phone that won't support those...
jsheard•1h ago
That ship already sailed, most legacy Android games were killed by 32bit support being phased out both in hardware (newer SOCs are 64bit only) and software (Android 14 doesn't support 32bit apps even when running on an older SOC). They've done it before and they'll do it again.
londons_explore•1h ago
Imagine a world where the page size is secret to userspace. Anything that needs page size alignment will be chosen by the kernel.
That in turn allows mixed page size, variable page size, heirarchical pages, etc.
Dylan16807•1h ago
duskwuff•1h ago
viraptor•45m ago