[Bug 1215663] # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
https://bugzilla.suse.com/show_bug.cgi?id=1215663 https://bugzilla.suse.com/show_bug.cgi?id=1215663#c5 Michal Koutný <mkoutny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoutny@suse.com, | |vvedomil@protonmail.com Flags| |needinfo?(vvedomil@protonma | |il.com) --- Comment #5 from Michal Koutný <mkoutny@suse.com> --- (In reply to Vědomil Vildomec from comment #0)
Could I ask to change that? Change config, build a kernel with CONFIG_SCHED_AUTOGROUP=y, and make the OpenSUSE kernel and the whole distro more friendly to gaming through Steam.
I'd suggest digging deeper for possible causes of the issue. Can you quantify the friendliness in comparison with basic enablement of CPU controller? [1] Or roughly describe what's the expected behavior? Would autogroup be needed nowadays at all? SCHED_AUTOGROUP was poorly justified feature (already in 2010) that can be realized purely in userspace by creating respective groups manually (or implicitly e.g. via PAM as would happen with pam_systemd when CPU controller is enabled). Don't let me start on combination of autogroups and regular groups (consider containers) in one system. I admit, I'm not a fan of enabling this config today. [1] E.g. override /usr/lib/systemd/system/user@.service.d/20-defaults-SUSE.conf with
cat >/etc/systemd/system/user@.service.d/60-cpu-delegation.conf <<EOD [Service] Delegate=cpu EOD -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com