From: "Jack O'Quin" <joq@io.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: hihone@bigpond.net.au, linux <linux-kernel@vger.kernel.org>,
CK Kernel <ck@vds.kolivas.org>,
rlrevell@joe-job.com, paul@linuxaudiosystems.com
Subject: Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling
Date: Tue, 18 Jan 2005 10:23:37 -0600 [thread overview]
Message-ID: <87y8eqso3a.fsf@sulphur.joq.us> (raw)
In-Reply-To: <41ED30EB.4090904@kolivas.org> (Con Kolivas's message of "Wed, 19 Jan 2005 02:53:15 +1100")
Con Kolivas <kernel@kolivas.org> writes:
> Cal wrote:
>
> 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.
Actually it makes perfect sense. Running non-realtime JACK threads
SCHED_FIFO will do the most harm. The others less.
I predict that using normal jackd -R (without schedtool) will produce
the same results running SCHED_FIFO and SCHED_ISO (within the normal
variance).
I think schedtool is too blunt and instrument for making these
measurements.
--
joq
next prev parent reply other threads:[~2005-01-18 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 13:01 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 [this message]
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=87y8eqso3a.fsf@sulphur.joq.us \
--to=joq@io.com \
--cc=ck@vds.kolivas.org \
--cc=hihone@bigpond.net.au \
--cc=kernel@kolivas.org \
--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
all inboxes | Powered by JetHome®