From: Con Kolivas <kernel@kolivas.org>
To: "Jack O'Quin" <joq@io.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Alexander Nyberg <alexn@dsv.su.se>,
Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: [PATCH] sched - Implement priority and fifo support for SCHED_ISO
Date: Tue, 01 Feb 2005 10:01:14 +1100 [thread overview]
Message-ID: <41FEB8BA.7000106@kolivas.org> (raw)
In-Reply-To: <87651di55a.fsf@sulphur.joq.us>
Jack O'Quin wrote:
> Con Kolivas <kernel@kolivas.org> writes:
>
>
>>Sure enough I found the bug in less than 5 mins, and it would
>>definitely cause this terrible behaviour.
>>
>>A silly bracket transposition error on my part :P
>
>
> The corrected version works noticeably better, but still nowhere near
> as well as SCHED_FIFO. The first run had a cluster of really bad
> xruns. The second and third were much better, but still with numerous
> small xruns.
>
> http://www.joq.us/jack/benchmarks/sched-iso-fix/
>
> With a compile running in the background it was a complete failure.
> Some kind of big xrun storm triggered a collapse on every attempt.
>
> http://www.joq.us/jack/benchmarks/sched-iso-fix+compile/
>
> The summary statistics are mixed. The delay_max is noticeably better
> than before, but still much worse than SCHED_FIFO. But, the xruns are
> really bad news...
Excellent.
Believe it or not these look like good results to me. Your XRUNS are
happening when the DSP load is >70% which is the iso_cpu % cutoff. Try
setting the iso_cpu to 90%
echo 90 > /proc/sys/kernel/iso_cpu
Cheers,
Con
next prev parent reply other threads:[~2005-01-31 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 9:47 [PATCH] sched - Implement priority and fifo support for SCHED_ISO Con Kolivas
2005-01-31 18:54 ` Jack O'Quin
2005-01-31 20:15 ` Con Kolivas
2005-01-31 20:30 ` Con Kolivas
2005-01-31 21:04 ` Jack O'Quin
2005-01-31 22:51 ` Jack O'Quin
2005-01-31 23:01 ` Con Kolivas [this message]
2005-02-01 2:27 ` Jack O'Quin
2005-02-01 2:46 ` Con Kolivas
2005-02-01 4:44 ` Jack O'Quin
2005-02-01 4:56 ` Con Kolivas
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=41FEB8BA.7000106@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=joq@io.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zwane@linuxpower.ca \
/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