From: Tim Blechmann <tim@klingt.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: rt file i/o
Date: Wed, 04 Nov 2009 16:52:07 +0100 [thread overview]
Message-ID: <4AF1A327.3040103@klingt.org> (raw)
In-Reply-To: <5bdc1c8b0911040743h7e4eaa08w97ac8287b806b54f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
> I'm not a developer and cannot really address your specific
> question but for my use of the rt-kernel I put important rt-audio
> files on a 1394 drive and give the 1394 driver higher priorities using
> the IRQ scheduling tools. I don't have any trouble running 2 or 3 1394
> drives recording and playing back 48 channels in Ardour.
>
> While I agree you should do everything the right way technically in
> the code maybe part of your solution is outside of the app you are
> writing and in the use of these support tools?
well, if i understand the rt howto correctly, _no_ disc access is
allowed, neither from rt nor from non-rt threads, since it may produce
page faults, which introduce latencies ...
according to this definition, ardour is not an rt-safe application ...
as for rt-safety, i prefer analyzing the latency hotspots instead of
relying on test results
tim
--
tim@klingt.org
http://tim.klingt.org
Avoid the world, it's just a lot of dust and drag and means nothing in
the end.
Jack Kerouac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-04 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 15:25 rt file i/o Tim Blechmann
2009-11-04 15:43 ` Mark Knecht
2009-11-04 15:52 ` Tim Blechmann [this message]
2009-11-04 17:14 ` Nicholas Mc Guire
2009-11-04 17:32 ` Tim Blechmann
2009-11-04 22:41 ` Nicholas Mc Guire
2009-11-04 22:44 ` Clark Williams
2009-11-05 4:30 ` Shane M Smith
2009-11-05 9:29 ` Tim Blechmann
2009-11-05 20:30 ` Remy Bohmer
2009-11-05 9:22 ` Sven-Thorsten Dietrich
2009-11-05 4:14 ` Mark Knecht
2009-11-04 17:09 ` Nicholas Mc Guire
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=4AF1A327.3040103@klingt.org \
--to=tim@klingt.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markknecht@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.