From: Pete <peterpion@yahoo.com>
To: John Rigg <aldev@sound-man.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Xrun stack trace for 1010LT
Date: Fri, 5 Dec 2008 08:11:36 -0800 (PST) [thread overview]
Message-ID: <434768.7988.qm@web65408.mail.ac4.yahoo.com> (raw)
In-Reply-To: <20081205160215.GA3295@localhost>
So even if the kernel is not a RT kernel, processes can run with real time priority? How is this so? From what ive read about the RT kernel it sounds like the kernel has to cooperate with the processes running on the system to allow a process to awaken (on an interrupt for instance). Otherwise the kernel will be stuck in some non interruptable state for some time, blocking the interrupt from being serviced - is that wrong?
If Jack has a way to grab higher priority through some other mechanisim, could I build this into arecord I wonder. I have of course tried nicing the process to very unnice.
John Rigg <aldev@sound-man.co.uk> wrote: On Fri, Dec 05, 2008 at 07:23:00AM -0800, Pete wrote:
> Is there likely to be any disadvantage to running arecord rather
> than say Jack to capture? Does (say) Jack read the card in a 'better'
> way?
jackd runs with realtime priority if -R option is specified
when starting it. Running it without -R produces xruns fairly
often, but with -R they almost never happen on a properly configured
system. I don't know if arecord can run with realtime priority.
John
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-12-05 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:18 Xrun stack trace for 1010LT Pete cat
2008-12-05 14:26 ` Takashi Iwai
2008-12-05 14:48 ` Pete cat
2008-12-05 15:17 ` John Rigg
2008-12-05 15:20 ` Pete
2008-12-05 15:23 ` Pete
2008-12-05 16:02 ` John Rigg
2008-12-05 16:11 ` Pete [this message]
2008-12-05 19:41 ` John Rigg
2008-12-05 21:39 ` Pete
2008-12-06 14:46 ` John Rigg
2008-12-15 15:23 ` Pete
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=434768.7988.qm@web65408.mail.ac4.yahoo.com \
--to=peterpion@yahoo.com \
--cc=aldev@sound-man.co.uk \
--cc=alsa-devel@alsa-project.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