From: Davide Libenzi <davidel@xmailserver.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ...
Date: Mon, 14 Jul 2003 08:09:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0307140805220.4371@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <5.2.1.1.2.20030714100438.01be5008@pop.gmx.net>
On Mon, 14 Jul 2003, Mike Galbraith wrote:
> At 12:12 AM 7/14/2003 -0700, Davide Libenzi wrote:
> >On Mon, 14 Jul 2003, Mike Galbraith wrote:
> > > While testing, I spotted something pretty strange. It's not specific to
> > > SCHED_SOFTRR, SCHED_RR causes it too. If I fire up xmms's gl visualization
> > > with either policy, X stops getting enough sleep credit to stay at a usable
> > > priority even when cpu usage is low. Fully repeatable weirdness. See
> > > attached top snapshots.
> >
> >RT tasks are pretty powerfull and should not be used to run everything ;)
> >What I was seeking with this patch was 1) deterministic latency 2) stave
> >protection.
>
> Yes, I know. I only fired up the cpu hog as a test to see that the
> protection would kick in. I did do that too though, ran _everything_...
> the whole X/KDE beast SCHED_SOFTRR for grins :)
>
> I should have reported the strangeness in a different thread, it has
> nothing to do with your patch.
Did you try the skip resistance test by running XMMS alone with audio ?
Also, trying the whole player running with SOFTRR does not match the
effective use MM apps will do of it. Usually inside MM apps the data
decoder (that might suck CPU) lives in another thread and the thread that
is actually responsible for timings simply fetch the prepared data.
- Davide
next prev parent reply other threads:[~2003-07-14 15:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.55.0307131442470.15022@bigblue.dev.mcafeelabs.c om>
2003-07-14 7:11 ` Mike Galbraith
2003-07-13 21:51 ` Davide Libenzi
2003-08-09 14:05 ` Daniel Phillips
2003-08-09 17:47 ` Mike Galbraith
2003-08-09 23:58 ` Daniel Phillips
2003-08-10 6:06 ` Mike Galbraith
2003-08-10 0:41 ` Daniel Phillips
2003-08-10 6:41 ` Mike Galbraith
2003-08-10 15:46 ` Daniel Phillips
2003-08-10 17:49 ` Mike Galbraith
2003-08-10 20:28 ` Daniel Phillips
2003-08-11 5:31 ` Mike Galbraith
2003-08-11 13:54 ` Takashi Iwai
2003-08-10 2:05 ` Roger Larsson
2003-08-10 5:43 ` Nick Piggin
2003-08-10 7:41 ` Mike Galbraith
2003-08-10 7:56 ` Nick Piggin
2003-08-10 8:18 ` Mike Galbraith
2003-08-10 9:19 ` jw schultz
2003-08-11 17:01 ` Roger Larsson
2003-08-11 17:25 ` Takashi Iwai
[not found] ` <200308100405.52858.roger.larsson@skelleftea.mail.telia.com >
2003-08-10 7:11 ` Mike Galbraith
2003-08-12 7:23 ` Rob Landley
2003-08-12 23:35 ` Pavel Machek
2003-08-13 6:26 ` Mike Galbraith
2003-08-13 9:41 ` Pavel Machek
2003-07-14 7:12 ` Davide Libenzi
2003-07-14 7:24 ` Jamie Lokier
2003-07-14 7:35 ` Davide Libenzi
2003-07-14 9:11 ` Mike Galbraith
[not found] ` <Pine.LNX.4.55.0307140004390.3435@bigblue.dev.mcafeelabs.co m>
2003-07-14 8:14 ` Mike Galbraith
2003-07-14 15:09 ` Davide Libenzi [this message]
[not found] ` <Pine.LNX.4.55.0307140805220.4371@bigblue.dev.mcafeelabs.co m>
2003-07-14 16:06 ` Mike Galbraith
2003-07-14 17:22 ` Davide Libenzi
[not found] ` <Pine.LNX.4.55.0307141015010.4828@bigblue.dev.mcafeelabs.co m>
2003-07-15 4:56 ` Mike Galbraith
2003-07-15 15:47 ` Davide Libenzi
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=Pine.LNX.4.55.0307140805220.4371@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=efault@gmx.de \
--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®