linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Guillaume Chazarain <gfc@altern.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] SCHED_ISO for interactivity
Date: Sun, 13 Jul 2003 22:53:12 +1000	[thread overview]
Message-ID: <200307132253.12883.kernel@kolivas.org> (raw)
In-Reply-To: <JEPOQNA0LFV95MFCPMSKONGFSNX.3f113751@monpc>

On Sun, 13 Jul 2003 20:41, Guillaume Chazarain wrote:
> Hi Con,
>
> I am currently testing SCHED_ISO, but I have noticed a regression:
> I do a make -j5 in linux-2.5.75/ everything is OK since gcc prio is 25.
> X and fvwm prio are 15, but when I move a window it's very jerky.

Interesting. I don't know how much smaller the timeslice can be before 
different hardware will be affected. Can you report what cpu and video card 
you're using? Unfortunately I don't have a range of hardware to test it on 
and I chose the aggressive 1/5th timeslice size. Can you try with ISO_PENALTY 
set to 2 instead?

> And btw, as I am interested in scheduler improvements, do you have a
> testcase where the stock scheduler does the bad thing? Preferably without
> KDE nor Mozilla (I don't have them installed, and I'll have access to a
> decent connection in september).

Transparency and antialiased fonts are good triggers. Launcing Xterm with 
transparency has been known to cause skips. Also the obvious make -j 4 kernel 
compiles, and 
while true ; do a=2 ; done
as a fast onset full cpu hog

> BTW2, you all seem to test interactivity with xmms. Just for those like me
> that didn't noticed, I have just found that it skips much less with alsa's
> OSS emulation than with alsa-xmms.

Anything that increases the signal to noise ratio at helping us pick up 
skips/problems is useful, but this can help those that _don't_ want skips so 
thanks.

> Thanks,

Thank you very much for testing and reporting.

Con


       reply	other threads:[~2003-07-13 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <JEPOQNA0LFV95MFCPMSKONGFSNX.3f113751@monpc>
2003-07-13 12:53 ` Con Kolivas [this message]
2003-07-14 15:40 [RFC][PATCH] SCHED_ISO for interactivity Guillaume Chazarain
2003-07-14 21:45 ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2003-07-13 14:54 Guillaume Chazarain
2003-07-14  0:07 ` Con Kolivas
2003-07-14  4:05 ` Con Kolivas
2003-07-13 10:41 Guillaume Chazarain
2003-07-13 11:54 ` Christian Axelsson
2003-07-13 14:06   ` Con Kolivas
2003-07-11 10:53 Con Kolivas
     [not found] ` <1068.::ffff:217.208.49.177.1057927722.squirrel@lanil.mine.nu>
2003-07-11 14:30   ` Con Kolivas
2003-07-11 23:37     ` Christian Axelsson
2003-07-12  0:13       ` Con Kolivas
2003-07-12 15:39         ` Con Kolivas
2003-07-12 16:27           ` Michael Buesch
2003-07-12 16:28           ` Christian Axelsson
2003-07-13  2:26             ` Con Kolivas
2003-07-13  3:40               ` Christian Axelsson
2003-07-13 20:07               ` Daniel Phillips
2003-07-12 15:49 ` William Lee Irwin III
2003-07-12 15:53   ` Con Kolivas
2003-07-13 20:03   ` Daniel Phillips
2003-07-14  0:13     ` Con Kolivas
2003-07-14  2:40       ` Daniel Phillips

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=200307132253.12883.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=gfc@altern.org \
    --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;
as well as URLs for NNTP newsgroup(s).