The 'patch' is no longer a patch: it was incorporated into the kernel 2.6.38 (see the link that Stupot
posted) and so has been active in all the SL kernels since then. So what you need to try is to disable
its functionality in the latest SL kernel, to see if it makes any difference to the performance on your machine. And there are three ways of doing that, as mentioned in the post I linked to earlier, namely:1.
Edit the kernel config of the latest SL kernel version and change CONFIG_SCHED_AUTOGROUP=y to CONFIG_SCHED_AUTOGROUP=n and rebuild the kernel (see HOWTO: Upgrade kernel using genkernel
Add the kernel boot parameter "noautogroup" (without the quotes) to your kernel boot line in the file /boot/grub/grub.cfg (either by directly editing it or by editing /etc/default/grub and running grub-mkconfig -o /boot/grub/grub.cfg).
Open a Konsole/Terminal window, log-in a root user and enter the command:
- Code: Select all
echo 0 > /proc/sysctl/kernel/sched_autogroup_enabled
Option No. 3 is the least worth trying as it won't force existing tasks back to the root group. I.e. it is not a conclusive test of whether or not the functionality that was first incorporated into the kernel at version 2.6.38 is the cause of your problem. Personally, I'd edit /boot/grub/grub.cfg as mentioned in Option 2 above, as that is quick and easy to do and you can just reboot and see if there is any change in performance.
Option 1 survives a reboot. To revert to the original kernel you could either reinstall the kernel image using the Entropy package manager or reverse the edit and rebuild the kernel. Option 2 survives a reboot. To revert to the original situation you just need to edit /etc/grub/grub.cfg and delete the "noautogroup". Option 3 does not survive a reboot. You are back to the original situation after you reboot.