From: Ingo Molnar <mingo@elte.hu>
To: Matthew <jackdachef@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20
Date: Sun, 30 Sep 2007 17:43:54 +0200 [thread overview]
Message-ID: <20070930154354.GD24077@elte.hu> (raw)
In-Reply-To: <e85b9d30709290411u4f48d716o3260bab7d71261ff@mail.gmail.com>
* Matthew <jackdachef@gmail.com> wrote:
> both cpus have a continous load of ~ 70% right now so I'll be starting
> up 9 instances of glxgears, below are some output & details of my
> system (cpu frequency switching is disabled since it doesn't work
> right now with the current bios version)
>
> short summary: unfortunately after starting glxgears everything
> stuttered a lot, don't know if it's expactable during that heavy load
> - just wanted to let you know; after having closed each instance of
> glxgears, everything was fine again ...
> cpu#0, 2404.249 MHz
> cpu#1, 2404.249 MHz
> result: most times only 2-3 of the glxgears-windows were running, the
> rest was stuttering / halting (no motion) mouse movement was pretty
> discountinous, keyboard input was also delayed
how does it behave without the cfs patch applied? Does it work better
under v20.5? The best debug output for me to look at would be to
download these two scripts:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info-clear.sh
first run cfs-debug-info-clear.sh, then use the system for a few minutes
and make sure apps are behaving in a 'stutter-free' way. Then run
cfs-debug-info.sh (still no glxgears running) - it will produce a "no
load" debug info file. Then start the 9x glxgears instances, reproduce
the "stuttering" behavior in the apps, and run cfs-debug-info.sh - this
will produce a second "under load" output file. Please send me both
output files.
also, what's the output of "glxgears -info" - does it render on real 3D
hardware, or uses the sw-mesa fallback?
Ingo
next prev parent reply other threads:[~2007-09-30 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 11:11 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Matthew
2007-09-30 15:43 ` Ingo Molnar [this message]
[not found] ` <e85b9d30709300943rded9801xddc6ca0a4773ff53@mail.gmail.com>
2007-09-30 16:45 ` Fwd: " Matthew
2007-09-30 17:27 ` Ingo Molnar
2007-09-30 23:54 ` Bill Davidsen
2007-10-02 9:06 ` Matthew
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 11:13 Ingo Molnar
2007-09-26 13:33 ` S.Çağlar Onur
2007-09-26 13:48 ` Ingo Molnar
2007-09-28 20:26 ` Alejandro Riveira Fernández
2007-09-29 2:20 ` Henrique de Moraes Holschuh
2007-09-29 16:51 ` Alejandro Riveira Fernández
2007-09-30 15:26 ` Ingo Molnar
2007-10-02 18:12 ` Alejandro Riveira Fernández
2007-10-26 18:56 ` [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8,v2.6.21.7, v2.6.20.20 Fortier,Vincent [Montreal]
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=20070930154354.GD24077@elte.hu \
--to=mingo@elte.hu \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.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