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>
Subject: Re: patch O1int for 2.5.73 - interactivity work
Date: 25 Jun 2003 23:53:01 +0200 [thread overview]
Message-ID: <1056577981.603.3.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200306260209.45020.kernel@kolivas.org>
On Wed, 2003-06-25 at 18:09, Con Kolivas wrote:
> Hi all
>
> I've used the corner cases described that cause a lot of the interactivity
> problems to develop this patch. What it does different to default (without
> nasty hacks) is the following:
>
> The interactivity is based on the max sleep avg (10s) as previously, unless
> the thread has been running for less than 10s. In that case it is based on
> the duration it has been running, with a minimum of 10 jiffies to estimate
> the interactivity (perhaps more might be appropriate here). This should
> minimise tasks taking ages to be categorised as interactive.
>
> If tasks sleep for a long time (>1s) they are no longer classified as
> interactive, but idle - meaning they receive their static priority. However,
> since they _may_ become interactive, the period over which the interactivity
> is estimated is decreased (1sec, perhaps can be reduced) so they may become
> interactive rapidly again. This should minimise idle tasks (like BASH) that
> suddenly become cpu hungry from stalling everything.
>
> I'm still working on something for the "xmms stalls if started during very
> heavy load" as a different corner case.
>
> This is only a compile tested patch (need sleep bad) but has been tested in
> 2.4 form and works nicely at avoiding those corner test cases.
>
> Please comment and test if you can.
This patch is indeed much better than the ones posted before. In fact,
it's really, really hard for me to make XMMS skip audio. It feels much
better in general, but there are still some rough edges when the system
is under load. For example, the mouse cursor on an X session doesn't
move smoothly, and feels a little jumpy. It can be somewhat fixed by
renicing the X server to -20.
Anyways, this is the best I've seen until date, and I'm currently
running on it. We'll see if it's up to expectations... at least, I think
so :-)
>
> Con
next prev parent reply other threads:[~2003-06-25 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 16:09 Con Kolivas
2003-06-25 19:00 ` Mike Galbraith
2003-06-25 19:34 ` Daniel Gryniewicz
2003-06-25 20:33 ` Mike Galbraith
2003-06-25 21:43 ` Con Kolivas
2003-06-25 21:53 ` Felipe Alfaro Solana [this message]
2003-06-25 23:10 ` Andy Pfiffer
2003-06-25 23:39 ` Con Kolivas
2003-06-26 20:16 ` Diego Calleja García
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=1056577981.603.3.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.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
all inboxes | Powered by JetHome®