From: Con Kolivas <kernel@kolivas.org>
To: hihone@bigpond.net.au
Cc: linux <linux-kernel@vger.kernel.org>,
CK Kernel <ck@vds.kolivas.org>,
joq@io.com, rlrevell@joe-job.com, paul@linuxaudiosystems.com
Subject: Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling
Date: Wed, 19 Jan 2005 02:53:15 +1100 [thread overview]
Message-ID: <41ED30EB.4090904@kolivas.org> (raw)
In-Reply-To: <41ED2F1F.1080905@bigpond.net.au>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Cal wrote:
> Con Kolivas wrote:
>
>> Comments and testing welcome.
>
>
> There's a collection of test summaries from jack_test3.2 runs at
> <http://www.graggrag.com/ck-tests/ck-tests-0501182249.txt>
>
> Tests were run with iso_cpu at 70, 90, 99, 100, each test was run twice.
> The discrepancies between consecutive runs (with same parameters) is
> puzzling. Also recorded were tests with SCHED_FIFO and SCHED_RR.
>
> Before drawing any hardball conclusions, verification of the results
> would be nice. At first glance, it does seem that we still have that
> fateful gap between "harm minimisation" (policy) and "zero tolerance"
> (audio reality requirement).
Thanks.
SCHED_ISO
/proc/sys/kernel/iso_cpu . . .: 70
/proc/sys/kernel/iso_period . : 5
XRUN Count . . . . . . . . . : 110
vs
SCHED_FIFO
XRUN Count . . . . . . . . . : 114
XRUN Count . . . . . . . . . : 187
vs
SCHED_RR
XRUN Count . . . . . . . . . : 0
XRUN Count . . . . . . . . . : 0
Something funny going on here... You had more xruns with SCHED_FIFO than
the default SCHED_ISO settings, and had none with SCHED_RR. Even in the
absence of the SCHED_ISO results, the other results dont make a lot of
sense.
Con
P.S. If you're running on SMP it may be worth booting on UP or using cpu
affinity (schedtool -a 0x1 will bind you to 1st cpu only) and see what
effect that is having. There are some interesting things that can
adversely affect latency on SMP.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-01-18 15:55 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 [this message]
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
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=41ED30EB.4090904@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=hihone@bigpond.net.au \
--cc=joq@io.com \
--cc=linux-kernel@vger.kernel.org \
--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