[6.6] [Feature]: enhance rich container for overcommit memory · Pull Request !4244 · anolis/cloud-kernel

bugzilla: https://bugzilla.openanolis.cn/show_bug.cgi?id=12437

Workloads running on the same host may require conflict configs of `overcommit_memory`. For example, redis prefers 1, and
postgresql prefers 2.

Add rich container extra data to support custom overcommit policy. Now, each container can set its own `/proc/sys/vm/overcommit*`.

It is known that some database applications require specific `overcommit_memory` config. Applications requiring `overcommit_memory=1` want to ensure fork is successful since memory will not actually be used, such as `redis`. Applications requiring `overcommit_memory=2`
usually check `mmap` status before using memory, and they would rather handle errors themselves than be killed by the oom-killer.

Here are some related links:
Redis (prefers 1): https://redis.io/docs/latest/operate/oss_and_stack/management/admin/#linux
PostgreSQL (prefers 2): https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT
Greenplum (prefers 2): https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-greenplum/7/greenplum-database/best_practices-sysconfig.html

This feature is a subset of vKernel which provides independent virtual kernels for containers to improve isolation. (See also https://gitee.com/joyallen/vkernel-doc/blob/master/README.md)

类型	指派人员	状态
审查	hsiangkao josephhz JeffleXu zhongjiang 赵鑫鹏陶义 vxuyu dtc baolin.wang	已完成 (0/0人)
测试	小龙已测试通过	已完成 (1/1人)

GVPanolis/cloud-kernel

搜索帮助

GVP anolis/cloud-kernel