Hi Ingo, I finally have a rebuilt kernel with latency tracing enabled, a jackd with the proper prctl incantations built in and I'm getting some (hopefully) meaningful data. I'm running a script that samples /etc/latency_trace every second and logs the maximums to a file. First attachment: jackd running 2x128 @48KHz, idle (no clients). Ignore the first trace (leftover from a previous run). After the first three triggered latencies I added a task doing a "tar cf usr.tar /usr" to see what disk i/o load would do. Second attachment: jackd + ams + japa + disk i/o Are these good for anything? [Maybe I need to just enable tracing all the time instead of just tracing inside the jack client loop?] -- Fernando
Attachment:
latencytraces-jack-idle.gz
Description: GNU Zip compressed data
Attachment:
latencytraces-jack-ams-japa.gz
Description: GNU Zip compressed data
- Follow-Ups:
- Re: 2.6.19-rt1: max latencies with jackd
- From: Ingo Molnar <[email protected]>
- Re: 2.6.19-rt1: max latencies with jackd
- Prev by Date: Re: [rfc patch] optimize o_direct on block device
- Next by Date: Re: [Bug 7505] Linux-2.6.19 fails to boot on AMD64 machine
- Previous by thread: Re: [Bugme-new] [Bug 7602] New: Failure on compilation: include/asm/bitops.h:122: error: inconsistent operand constraints in an `asm' in nfs_access_add_cache()
- Next by thread: Re: 2.6.19-rt1: max latencies with jackd
- Index(es):