Speakers
Description
With the release of Android 17, partners are required to support the 16 KB developer option on devices meeting specific hardware requirements, such as CPU compatibility and memory configurations exceeding 8 GiB. While this transition significantly improves system performance and unlocks hardware efficiencies, Android partners frequently observe a noticeable memory footprint increase, and they ask "How can we reduce this memory footprint?". This regression is primarily driven by internal fragmentation, mapping more memory than what is needed and page-granularity alignment constraints across both userspace and kernel allocations.
This presentation provides a concrete, engineering-focused recipes for Partners to reduce the memory footprint in:
Userspace
- Fileback mappings
- Anonymous Memory
- Shmem memory
Kerne memory
- Kernel modules
- CMA memory usage
- Buffer allocations in drivers