From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>, Sam Ravnborg <sam@ravnborg.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date: Mon, 28 Jan 2008 16:16:02 +0100 [thread overview]
Message-ID: <200801281616.04649.toralf.foerster@gmx.de> (raw)
In-Reply-To: <20080128131823.GB8269@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
Hello,
At Monday 28 January 2008 Ingo Molnar wrote :
>
> it splits the CPU time between Xorg (root UID) and desktop apps. This
> helps particularly well when there's compile jobs going on, etc. - Xorg
good news for all Gentoo users ;)
> So if you have some time to play with this, could you please try the
> following experiment. Put the following line into your
> /etc/rc.d/rc.local file:
>
> echo 2 > /sys/kernel/uids/`grep -w dnetc /etc/passwd | cut -d: -f3`/cpu_share
>
> with group scheduling (CONFIG_FAIR_GROUP_SCHED=y) enabled. Also apply
> the patch attached below as well - which fixes some interactivity
> problems with group scheduling.
> Could you try that kernel and compare it to a FAIR_GROUP_SCHED-disabled
> kernel's interactivity, and send us your observations?
With the patch and the sysfs-option my system works ok and last but not least
with the expected behaviour compared to a previous kernel.
In addition my first impression is that its responseness is better compared to
previous kernel versions and nearly the same compared to a kernel without
FAIR_GROUP_SCHED .
Compared to kernel 2.6.23 the 1-liner "time factor 819734028463158891" needs
now ~5.61 sec which is a little bit higher than the previous value of 5.44 sec.
Thanks for the solution (BTW b/c FAIR_GROUP_SCHED defaults to "y" I could bet
that more peoples run into this case).
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-28 15:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:11 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster
2008-01-27 14:46 ` Srivatsa Vaddagiri
2008-01-27 15:06 ` Toralf Förster
2008-01-27 16:54 ` Srivatsa Vaddagiri
2008-01-27 16:57 ` Toralf Förster
2008-01-27 21:27 ` Peter Zijlstra
2008-01-27 22:32 ` Ingo Molnar
2008-01-28 8:38 ` Helge Hafting
2008-01-26 21:38 ` Toralf Förster
2008-01-26 21:45 ` Sam Ravnborg
[not found] ` <200801271200.04971.toralf.foerster@gmx.de>
[not found] ` <1201433167.22060.10.camel@homer.simson.net>
2008-01-27 12:39 ` Toralf Förster
2008-01-27 18:58 ` Mike Galbraith
2008-01-27 21:14 ` Toralf Förster
2008-01-27 21:25 ` Peter Zijlstra
2008-01-28 13:18 ` Ingo Molnar
2008-01-28 15:16 ` Toralf Förster [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-26 14:06 Toralf Förster
2008-02-04 0:32 ` Andrew Morton
2008-02-04 0:36 ` Andrew Morton
2008-02-04 17:44 ` Pallipadi, Venkatesh
2008-02-04 19:18 ` Toralf Förster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801281616.04649.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®