←back to thread

Transition to using 16 KB page sizes for Android apps and games

(android-developers.googleblog.com)
95 points ingve | 4 comments | 11 Jul 25 07:04 UTC | HN request time: 0.782s | source
1. londons_explore ◴[15 Jul 25 06:47 UTC] No.44568552[source]▶
If you're making the migration at all, you really ought to be going for fully variable page sizes, otherwise 5 years from now there'll be a 64K page size CPU and suddenly everyone has to recompile everything again and there is another compatibility wall...
replies(2): >>44568703 #>>44575914 #
2. rwmj ◴[15 Jul 25 07:09 UTC] No.44568703[source]▶
Is there a such a thing? Page size gets baked into things like executable layouts, plus any place that uses the PAGE_SIZE constant (instead of sysconf(_SC_PAGESIZE)).
replies(1): >>44569886 #
3. londons_explore ◴[15 Jul 25 11:02 UTC] No.44569886[source]▶
Indeed it would take redesigning a bunch of things to make runtime variable page size an option.
4. bjourne ◴[15 Jul 25 21:17 UTC] No.44575914[source]▶
4 KiB page sizes have been used since the 1960's. More memory doesn't necessarily mean that larger pages are beneficial. Maybe 16 KiB is better for Android? Maybe. There really is no clear consensus on what the optimal page size for modern architectures should be.