From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Scheduler: -mm vs -staircase
Date: Sat, 26 Jun 2004 00:56:54 +0200 [thread overview]
Message-ID: <20040625225654.GC4453@werewolf.able.es> (raw)
In-Reply-To: <20040625221042.GA4453@werewolf.able.es> (from jamagallon@able.es on Sat, Jun 26, 2004 at 00:10:42 +0200)
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
On 06.26, J.A. Magallon wrote:
> Hi all...
>
> Just a comment about a weird thing I have noticed wrt scheduling in latest
> kernels.
>
> My last two tests are 2.6.7-mm2 and 2.6.7-mm2+staircase-7.4 (plus a couple
> other things, like aic updated driver). I use GLMatrix as screensaver,
> running with nVidia drivers (yup, tainted kernels, but both are tainted ;)).
> What I have noticed:
> - With standard -mm, as GLMatrix runs, the framerate drops even to something
> like a frame every couple seconds
> - With staircase, it keeps running smoothly at 25fps.
>
> Something is strange in -mm. It keeps stoling cycles to the screensaver.
> Is this expected ?
>
Sorry for the noise, it also happens with -staircase.
Lets remake the question.
I start /usr/lib/xscreensaver/glmatrix -fps, and the frame rate starts at
25 fps. In 30 seconds it has dropped to 6 fps. The app is still using
the same cpu time (about 90% of one cpu on a dual xeon box with ht).
Any ideas ?
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Cooker) for i586
Linux 2.6.7-jam5 (gcc 3.4.1 (Mandrakelinux (Cooker) 3.4.1-0.3mdk)) #1
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-25 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 22:10 Scheduler: -mm vs -staircase J.A. Magallon
2004-06-25 22:56 ` J.A. Magallon [this message]
2004-06-25 23:26 ` Diego Calleja García
2004-06-25 23:37 ` Diego Calleja García
2004-06-25 23:39 ` J.A. Magallon
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=20040625225654.GC4453@werewolf.able.es \
--to=jamagallon@able.es \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.