From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Mike Galbraith <efault@gmx.de>,
Davide Libenzi <davidel@xmailserver.org>,
Mike Fedyk <mfedyk@matchmail.com>,
Wiktor Wodecki <wodecki@gmx.net>,
Eugene Teo <eugene.teo@eugeneteo.net>,
Danek Duvall <duvall@emufarm.org>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [PATCH] O8int for interactivity
Date: 23 Jul 2003 18:46:24 +0200 [thread overview]
Message-ID: <1058978784.740.4.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200307232155.27107.kernel@kolivas.org>
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 :-)
next prev parent 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:
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=1058978784.740.4.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@osdl.org \
--cc=davidel@xmailserver.org \
--cc=duvall@emufarm.org \
--cc=efault@gmx.de \
--cc=eugene.teo@eugeneteo.net \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=wli@holomorphy.com \
--cc=wodecki@gmx.net \
/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).