Bug 23938 - kernel-desktop should enable CONFIG_MEMCG (Memory Cgroup Controller)
Summary: kernel-desktop should enable CONFIG_MEMCG (Memory Cgroup Controller)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-03 15:09 CET by Rémi Verschelde
Modified: 2018-12-04 10:13 CET (History)
2 users (show)

See Also:
Source RPM: kernel-4.19.6-2.mga7
CVE:
Status comment:


Attachments

Description Rémi Verschelde 2018-12-03 15:09:27 CET
Trying to use containers (via Neal Gompa's podman from https://copr.fedorainfracloud.org/coprs/ngompa/containers-mga) on Cauldron with recent kernel-desktop (4.19.5-something), I ran into blocking issues (and hard to debug, as no other podman user seemed affected).

It turns out that we don't enable the Memory Cgroup Controller feature (CONFIG_MEMCG) in kernel-desktop, while it is assumed available by container software nowadays.

Relevant bug reports: bug 12629 and bug 4203. It seems that back then the feature implied a significant overhead and was thus enabled only on kernel-server, but from what I understand it should now be safe (and necessary!) to have it on kernel-desktop too.
Rémi Verschelde 2018-12-03 15:09:39 CET

CC: (none) => ngompa13, tmb

Comment 1 Rémi Verschelde 2018-12-03 15:10:26 CET
(Thanks to Hein-Pieter van Braam for helping me debug this.)
Comment 2 Thomas Backlund 2018-12-03 17:19:50 CET
Agreed, the overhead is not as big today, and x86_64 hw is more powerful nowdays too..

and since there is now usecases for desktop users too the feature weights more than the overhead.

Changed in svn for aarch64 and x86_64 desktop users so it will be in kernel > 4.19.6-desktop-2.mga7

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 3 Rémi Verschelde 2018-12-04 10:13:03 CET
Thanks!

Note You need to log in before you can comment on or make changes to this bug.