From: Con Kolivas <kernel@kolivas.org>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Andreas Boman <aboman@midgaard.us>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] sleep_decay for interactivity 2.5.72 - testers needed
Date: Mon, 23 Jun 2003 01:58:45 +1000 [thread overview]
Message-ID: <200306230158.45201.kernel@kolivas.org> (raw)
In-Reply-To: <1056296401.712.9.camel@teapot.felipe-alfaro.com>
On Mon, 23 Jun 2003 01:40, Felipe Alfaro Solana wrote:
> On Sun, 2003-06-22 at 15:45, Con Kolivas wrote:
> > > Feel free to test it and comment. Things to look for - the dreaded
> > > audio skip under load, and X remaining interactive during sustained use
> > > under load.
>
> I must say this seems to be getting better, but I still prefer Mike's
> patches. With the latest sleep decay patch and 2.5.72-mm3, I can still
> easily starve XMMS audio for a long time (~5 seconds) on my 700Mhz
> Pentium III laptoñ (running RHL9 and KDE 3.1.2) simply by running "while
> true; do a=2; done" on a konsole window. Dragging a window fast enough
> also starves XMMS for ~5 seconds just until the scheduler adjusts the
> priorities.
>
> XMMS is running with an effective priority of 15 (that's what top says).
> "while true; do a=2; done" starts with a priority of 15 (which causes
> XMMS to stop playing sound), then it is detected as a CPU hog and every
> second its priority is increased by one. When its priority reaches 20,
> XMMS starts playing again.
>
> When I move windows around fast enough. the X server starts with a
> priority of 15, starving XMMS. If I keep moving windows around for a
> long time, X's priority starts increasing by one, until it reaches 20.
> At this moment, it stops disturbing XMMS audio playback.
>
> I've been playing with scheduler parameters, mainly by reducing
> MAX_SLEEP_AVG to (HZ) and STARVATION_LIMIT to (HZ). This seems to help a
> lot, although I can still make XMMS skip sound every once a bit.
> However, mplayer is a really hard one: I have been unable to make it
> skip sound yet.
Yes Mike's patches are definitely better. My patches are designed for the
2.4-ck patchset which has other workarounds that augment this patch; however
these workarounds are harder to stomach for mainstream kernels (read nasty
hacks). I thought I'd offer the not so nasty sleep_decay patch in 2.5 form
for perusal and comments since people are more willing to test 2.5 patches.
Con
next prev parent reply other threads:[~2003-06-22 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 14:05 [PATCH] sleep_decay for interactivity 2.5.72 - testers needed Con Kolivas
2003-06-19 15:47 ` Mike Galbraith
2003-06-19 15:51 ` Con Kolivas
2003-06-19 16:02 ` Con Kolivas
2003-06-19 16:06 ` Con Kolivas
2003-06-19 16:42 ` Andreas Boman
2003-06-19 16:50 ` Con Kolivas
[not found] ` <1056058342.917.69.camel@asgaard.midgaard.us>
2003-06-20 2:29 ` Con Kolivas
2003-06-20 11:09 ` Mike Galbraith
2003-06-22 13:35 ` Con Kolivas
2003-06-22 13:45 ` Con Kolivas
2003-06-22 15:40 ` Felipe Alfaro Solana
2003-06-22 15:58 ` Con Kolivas [this message]
2003-06-22 16:14 ` Felipe Alfaro Solana
2003-06-22 21:24 ` Con Kolivas
2003-06-22 21:37 ` Con Kolivas
2003-06-23 11:16 ` Felipe Alfaro Solana
2003-06-23 11:21 ` Con Kolivas
2003-06-19 17:31 ` Mike Galbraith
2003-06-19 18:51 ` Andreas Boman
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=200306230158.45201.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=aboman@midgaard.us \
--cc=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.