From: "Jack O'Quin" <joq@io.com>
To: Con Kolivas <kernel@kolivas.org>
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>, Rui Nuno Capela <rncbc@rncbc.org>
Subject: Re: [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling
Date: Wed, 19 Jan 2005 19:21:23 -0600 [thread overview]
Message-ID: <87pt00gajw.fsf@sulphur.joq.us> (raw)
In-Reply-To: <41EEF649.4070705@kolivas.org> (Con Kolivas's message of "Thu, 20 Jan 2005 11:07:37 +1100")
Con Kolivas <kernel@kolivas.org> writes:
> Jack O'Quin wrote:
>> Try again with JACK 0.99.48. It's in CVS now, but you probably need
>> this tarball to get around the dreaded SourceForge anon CVS lag...
>>
>> http://www.joq.us/jack/tarballs/jack-audio-connection-kit-0.99.48.tar.gz
>
> Thanks it finally ran to completion. By the way the patch you sent
> with the test suite did not apply so I had to do it manually
> (booraroom..)
Oops! Sorry. I generated those by hand using some rather crude
`diff -u .... >> xxx.diff' commands.
We should just add Rui's latest version to JACK CVS.
> Since I (finally) have it running at this end at last I'll do some
> benchmarking of my own to see how (lack of) priorities affects
> SCHED_ISO. If it is inadequate, it wont be too difficult to add them
> to the design. The problem with priorities is that once you go over
> the cpu limit everyone suffers equally; but that's a failsafe that you
> shouldn't actually hit in normal usage so it probably doesn't
> matter...
I'd be surprised if we're hitting it in this test. AFAICT, our
"Average DSP Load" should approximate your CPU limit. That's running
in the 30% to 40% range. Is there any way to verify this? Is your
running average readable in /proc/sys/kernel somewhere?
We do need to test that the system degrades gracefully when the CPU is
overloaded. That *will* happen (the dreaded P4 float denormal
problems quickly come to mind). At some point, the user should be
allowed to choose how much CPU to consume, possibly shutting down
plugins as needed.
> Hmm come to think of it, it probably _is_ a good idea to implement
> priority support afterall.
Hard to say for sure without trying it. These threads are dealing
with a realtime cycle that is smaller than normal scheduler time
slices. Getting all the work done is important. But, getting it done
in the right order might make a difference for important statistics
like Max Delay.
--
joq
prev parent reply other threads:[~2005-01-20 1:19 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
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 [this message]
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=87pt00gajw.fsf@sulphur.joq.us \
--to=joq@io.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul@linuxaudiosystems.com \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.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®