Message ID | 20210108174808.1550128-5-cascardo@canonical.com |
---|---|
State | New |
Headers | show |
Series | [SRU,xenial/linux-kvm] UBUNTU: [Config]: set CONFIG_BASE_FULL | expand |
diff --git a/debian.kvm/config/config.common.ubuntu b/debian.kvm/config/config.common.ubuntu index f5d48d9f154b..debb0a8100d1 100644 --- a/debian.kvm/config/config.common.ubuntu +++ b/debian.kvm/config/config.common.ubuntu @@ -153,8 +153,8 @@ CONFIG_AUTOFS4_FS=y # CONFIG_AUXDISPLAY is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # CONFIG_BACKTRACE_SELF_TEST is not set -# CONFIG_BASE_FULL is not set -CONFIG_BASE_SMALL=1 +CONFIG_BASE_FULL=y +CONFIG_BASE_SMALL=0 # CONFIG_BATMAN_ADV is not set # CONFIG_BCACHE is not set # CONFIG_BCMA is not set
BugLink: https://bugs.launchpad.net/bugs/1866149 Which, in turn, leads to CONFIG_BASE_SMALL=0. This turns off some memory savings that linux-kvm carried. Those savings, however, are minimal, and do not justify the runtime penalty and did not account to significant boot time savings. This also lead to a limit in PIDs on the system that caused degraged boot when systemd-sysctl tried to change the default maximum PID. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com> --- debian.kvm/config/config.common.ubuntu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)