From: Con Kolivas <kernel@kolivas.org>
To: "Jack O'Quin" <joq@io.com>
Cc: linux <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
rlrevell@joe-job.com, paul@linuxaudiosystems.com,
CK Kernel <ck@vds.kolivas.org>
Subject: Re: [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling
Date: Wed, 19 Jan 2005 20:33:59 +1100 [thread overview]
Message-ID: <41EE2987.1040005@kolivas.org> (raw)
In-Reply-To: <87is5tx61a.fsf@sulphur.joq.us>
[-- Attachment #1: Type: text/plain, Size: 4001 bytes --]
Jack O'Quin wrote:
> Con Kolivas <kernel@kolivas.org> writes:
>
>
>>This patch for 2.6.11-rc1 provides a method of providing real time
>>scheduling to unprivileged users which increasingly is desired for
>>multimedia workloads.
>
>
> I ran some jack_test3.2 runs with this, using all the default
> settings. The results of three runs differ quite significantly for no
> obvious reason. I can't figure out why the DSP load should vary so
> much.
I installed a fresh jack installation and got the test suite. I tried
running the test suite and found it only ran to completion if I changed
the run time right down to 30 seconds from 300. Otherwise it bombed out
almost instantly at the default of 300. I don't know if that helps you
debug the problem or not but it might be worth mentioning.
As for my own results I gave it a run on the weak SCHED_ISO
implementation in 2.6.10-ck5 (P4HT 3.06):
SCHED_NORMAL:
*********************************************
Timeout Count . . . . . . . . :( 0)
XRUN Count . . . . . . . . . : 74
Delay Count (>spare time) . . : 0
Delay Count (>1000 usecs) . . : 0
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 1046 usecs
Average DSP Load. . . . . . . : 18.0 %
Average CPU System Load . . . : 2.5 %
Average CPU User Load . . . . : 7.8 %
Average CPU Nice Load . . . . : 0.1 %
Average CPU I/O Wait Load . . : 0.1 %
Average CPU IRQ Load . . . . : 0.1 %
Average CPU Soft-IRQ Load . . : 0.0 %
Average Interrupt Rate . . . : 1776.0 /sec
Average Context-Switch Rate . : 10290.4 /sec
*********************************************
SCHED_NORMAL nice -n -20:
*********************************************
Timeout Count . . . . . . . . :( 0)
XRUN Count . . . . . . . . . : 266
Delay Count (>spare time) . . : 0
Delay Count (>1000 usecs) . . : 0
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 2239 usecs
Average DSP Load. . . . . . . : 28.6 %
Average CPU System Load . . . : 2.9 %
Average CPU User Load . . . . : 10.2 %
Average CPU Nice Load . . . . : 0.0 %
Average CPU I/O Wait Load . . : 1.0 %
Average CPU IRQ Load . . . . : 0.2 %
Average CPU Soft-IRQ Load . . : 0.1 %
Average Interrupt Rate . . . : 2049.7 /sec
Average Context-Switch Rate . : 10145.1 /sec
*********************************************
SCHED_ISO:
*********************************************
Timeout Count . . . . . . . . :( 0)
XRUN Count . . . . . . . . . : 1
Delay Count (>spare time) . . : 0
Delay Count (>1000 usecs) . . : 0
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 687 usecs
Average DSP Load. . . . . . . : 19.9 %
Average CPU System Load . . . : 2.6 %
Average CPU User Load . . . . : 10.3 %
Average CPU Nice Load . . . . : 0.0 %
Average CPU I/O Wait Load . . : 0.0 %
Average CPU IRQ Load . . . . : 0.2 %
Average CPU Soft-IRQ Load . . : 0.3 %
Average Interrupt Rate . . . : 2166.2 /sec
Average Context-Switch Rate . : 10117.3 /sec
*********************************************
SCHED_FIFO:
*********************************************
Timeout Count . . . . . . . . :( 0)
XRUN Count . . . . . . . . . : 2
Delay Count (>spare time) . . : 0
Delay Count (>1000 usecs) . . : 0
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 544 usecs
Average DSP Load. . . . . . . : 19.5 %
Average CPU System Load . . . : 3.1 %
Average CPU User Load . . . . : 12.6 %
Average CPU Nice Load . . . . : 0.0 %
Average CPU I/O Wait Load . . : 0.0 %
Average CPU IRQ Load . . . . : 1.0 %
Average CPU Soft-IRQ Load . . : 1.1 %
Average Interrupt Rate . . . : 5018.4 /sec
Average Context-Switch Rate . : 10902.5 /sec
*********************************************
It occasionally would segfault on client exit as well (as you've already
mentioned). I think we're still in the dark here to be honest.
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-01-19 9:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 13:01 [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling Con Kolivas
2005-01-18 14:53 ` Con Kolivas
2005-01-18 15:45 ` [ck] " Cal
2005-01-18 15:53 ` Con Kolivas
2005-01-18 16:23 ` Jack O'Quin
2005-01-18 16:17 ` Jack O'Quin
2005-01-19 2:02 ` Lee Revell
2005-01-19 2:08 ` Con Kolivas
2005-01-19 5:26 ` utz
2005-01-19 5:31 ` Con Kolivas
2005-01-19 14:01 ` Con Kolivas
2005-01-19 6:54 ` Jack O'Quin
2005-01-19 7:56 ` Con Kolivas
2005-01-19 14:27 ` Jack O'Quin
2005-01-19 9:33 ` Con Kolivas [this message]
2005-01-19 17:12 ` Jack O'Quin
2005-01-20 0:07 ` Con Kolivas
2005-01-20 1:21 ` Jack O'Quin
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=41EE2987.1040005@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=joq@io.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.com \
/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