archive mirror
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <>
To: Con Kolivas <>
Cc: linux kernel mailing list <>,
	Andrew Morton <>, Mike Galbraith <>,
	Davide Libenzi <>,
	Mike Fedyk <>,
	Wiktor Wodecki <>,
	Eugene Teo <>,
	Danek Duvall <>,
	William Lee Irwin III <>
Subject: Re: [PATCH] O8int for interactivity
Date: 23 Jul 2003 18:46:24 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 2003-07-23 at 13:55, Con Kolivas wrote:
> Here is an addon to the interactivity work so far. As the ability to become 
> interactive was made much faster and easier in O6*, I was able to remove a lot 
> of extra code uneeded in this latest patch, and remove a lot of the noticable 
> unfairness in the code. This is closer to the original scheduler code after 
> all these patches than any of my previous patches. All of O8int is aimed
> at fixing unfairness in my interactivity patches.

Testing it right now on top of 2.6.0-test1-mm2 :-)

Overall it feels better. I can't make XMMS skip at all. Under low load,
X is very smooth, but X is still jerky/jumpy when the system is under
heavy load (while true; do a=2; done) and I start moving windows all
around my KDE desktop. Renicing the X server to -20 makes it very smooth
under load (yeah, I know I shouldn't do this).

I'm playing a bit with tunables to see if I can tune the scheduler a
little bit for my system/workload. I've had good results reducing max
timeslice to 100 (yeah, I know I shouldn't do this too).

Will keep you informed :-)

  reply	other threads:[~2003-07-23 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 11:55 [PATCH] O8int for interactivity Con Kolivas
2003-07-23 16:46 ` Felipe Alfaro Solana [this message]
2003-07-24 16:12   ` Szonyi Calin
2003-07-24 22:20     ` Con Kolivas
2003-07-26  9:03   ` Eugene Teo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).