15 Feb
2016
15 Feb
'16
2:49 p.m.
On Mon, 15 Feb 2016 12:07:31 +0100
Joakim Hernberg <jhernberg(a)alchemy.lu> wrote:
> RTIRQ_NAME_LIST="snd_ice1712"
Most likely the RTC isn't used at all anymore,
check how many times it
has fired with "cat /proc/interrupts". One my system it fires exactly
once during bootup.
Indeed, that's the case. So no need whatsoever to prioritize rtc in
rtirq.
AFAIK, the only important configuration nowdays is to
make sure that
the soundcard (or usb hub is connected to) is executed first, then
JACK (which automatically gives the priority of your audio processing
threads). So I'd suggest to run the soundcard interrupt at a high
priority, say 95-97 or so (leave 99 for the housekeeping threads).
Then run JACK at 80 (which will run your audio processing threads at
75).
Sounds fine, if I may do a blatant pun.
top shows the following (hopefully the lines will not be warped in
email) :
PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
20 0 5782316 2,821g 133576 S 62,9 18,4 118:16.33 mixbus-3.1.66
9 -11 219472 90804 83556 S 2,3 0,6 4:33.85 jackd
The priority PR is way out for both. I know of the nice command,
although how can a higher priority be written into the system
configuration as to no adjust it at every boot ?