From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] N1int for interactivity
Date: 16 Jul 2003 09:12:00 +0200 [thread overview]
Message-ID: <1058339520.586.3.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200307160912.05833.kernel@kolivas.org>
On Wed, 2003-07-16 at 01:12, Con Kolivas wrote:
> > I can still starve XMMS on 2.5.75-mm1 + patch-O5int-0307150857 +
> > patch-N1int-0307152010:
> >
> > 1. Log on to KDE
> > 2. Launch Konqueror
> > 3. Launch XMMS and make it play
> > 4. Move Konqueror window all over the desktop
> >
> > Step 4 will make XMMS starve for a few seconds. Also, under heavy load
> > (while true; do a=2; done), moving the Konqueror window like crazy makes
> > X go jerky after a few seconds. If I quit moving windows around, after a
> > few other seconds, X returns to normal/smooth behavior.
>
> I was more concerned to see if the N1 patch added anything to the current
> behaviour, but that is abandoned work now so don't worry. I can address these
> further issues incrementally if you're willing to test them. My test boxes
> have been tamed but I need and appreciate greatly your testing.
Just throw anything to me and I will test it gladly :-)
> > I can fix the starvation/smoothness by setting:
> >
> > #define PRIO_BONUS_RATIO 45
> > #define INTERACTIVE_DELTA 4
> > #define MAX_SLEEP_AVG (HZ)
> > #define STARVATION_LIMIT (HZ)
> >
> > For me, 2.6.0-test1 stock scheduler plus above changes makes the most
> > user-friendly desktop I've ever seen.
>
> With a max sleep avg of just one second you'll never starve X or xmms for
> sustained periods; but under load X will not be smooth getting jerky even
> with small bursts of heavy X use; that's why Ingo increased the max sleep avg
> in the first place... but that led to other issues...
Well, under heavy load (while true ...) X still feels very smooth with
2.6.0-test1 and the above changes. In fact, I was inclined to make those
changes as X didn't feel smooth under load on my system without them.
prev parent reply other threads:[~2003-07-16 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 3:55 [PATCH] N1int for interactivity Con Kolivas
2003-07-15 3:59 ` Andrew Morton
2003-07-15 4:03 ` Con Kolivas
2003-07-15 7:02 ` Mike Galbraith
2003-07-15 7:00 ` Zwane Mwaikambo
2003-07-15 10:23 ` Con Kolivas
2003-07-15 15:23 ` Felipe Alfaro Solana
2003-07-15 23:12 ` Con Kolivas
2003-07-16 7:12 ` Felipe Alfaro Solana [this message]
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=1058339520.586.3.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.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).