16KB Page Size Support
summary
Testing 16KB base pages on a Pixel 6 shows concrete wins and concrete costs: binary load experiments report 4x fewer page faults and reduced ad-load latencies — 3% on average, 16% for Search, 30% for News — plus measurable power savings, but larger ELF segment alignment and page-granularity padding increase memory use and kernel bookkeeping by 25–30 MB at boot. Compatibility work includes loader fixes or VMA coalescing, a risky RWX fallback, failed binary-rewrite attempts, UFS and firmware-driver mismatches, and an x86 emulator that presents 16K to userspace while using 4K underneath.
AI-written summary · about
chapters (7)
- 0:00Introduction to 16k Pages
- 1:25Technical Background
- 3:24Fragmentation and Solutions
- 4:52Running 4k Apps
- 6:06Driver Issues and Fixes
- 8:02X86 Emulation Challenges
- 13:14Performance and Conclusion
related talks
38mEmbracing 16 KB Page Sizes in Android
21mPrepare your app for the 16 KB page migration
26mBootloops & Coffee: The Daily Grind of an AOSP Developer
49mTrash Talk
25mReducing Android Boot Times: Evaluating Proactive File Prefetching
08mKeep your app from failing in a 64-bit only world
08h 39mLivestream | Day 2, theater 2
40mTrash talk