SuSE 9.2, kernel.HZ, ,kernel.min-timeslice, kernel.def-timeslice
I'm trying to solve a problem of unusably slow KDE on my new 9.2 Pro install, http://lists.suse.com/archive/suse-linux-e/2004-Dec/1198.html. It seems that my HZ setting from grub and timeslice settings from sysconfig/kernel are not taking effect. I removed 'desktop' from menu.lst so it now reads: kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x317 selinux=0 splash=verbose resume=/dev/hda1 elevator=as showopts In sysconfig/kernel I set the timeslices as: SCHED_MINTIMESLICE="1000" SCHED_MAXTIMESLICE="30000" Yet after a couple of reboots 'sysctl -a' shows: kernel.HZ = 1000 kernel.min-timeslice = 5000 kernel.def-timeslice = 105000 How do I get my settings to stick? Also, where can I find documentation on all the options available to the kernel line in grub's menu.lst? Jason Joines =================================
Jason Joines wrote:
I'm trying to solve a problem of unusably slow KDE on my new 9.2 Pro install, http://lists.suse.com/archive/suse-linux-e/2004-Dec/1198.html.
It seems that my HZ setting from grub and timeslice settings from sysconfig/kernel are not taking effect. I removed 'desktop' from menu.lst so it now reads: kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x317 selinux=0 splash=verbose resume=/dev/hda1 elevator=as showopts
In sysconfig/kernel I set the timeslices as: SCHED_MINTIMESLICE="1000" SCHED_MAXTIMESLICE="30000"
Yet after a couple of reboots 'sysctl -a' shows: kernel.HZ = 1000 kernel.min-timeslice = 5000 kernel.def-timeslice = 105000
How do I get my settings to stick? Also, where can I find documentation on all the options available to the kernel line in grub's menu.lst?
Jason Joines =================================
I rebooted a couple of times and kernel.def-timeslice was different every time. Turns out I didn't have boot.sched enabled. That seems odd since I had just done a new install. I enabled it and went through the script. Now it's doing what it's supposed to. What happened to kernel.max-timeslice? Another related question. I looked at the running kernel configuration and noticed that 'CONFIG_PREEMPT is not set'. Is this setting the timeslice values to something recommended for desktops and alternative to preempting? Another odd thing I noticed immediately after the install finished was that nothing was being logged. If I tried to run rcsyslog manually I got no output. After going through that script it turned out that the binary for syslog to use was set to syslog-ng but syslogd was installed and not syslog-ng.
participants (1)
-
Jason Joines