linux-kernel - 2.6.19-rt1: max latencies with jackd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1164923245.31959.49.camel@cmn3.stanford.edu>
Date:	Thu, 30 Nov 2006 13:47:25 -0800
From:	Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
To:	Ingo Molnar <mingo@...e.hu>,
	"Linux-Kernel," <linux-kernel@...r.kernel.org>
Cc:	nando@...ma.Stanford.EDU
Subject: 2.6.19-rt1: max latencies with jackd

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

Download attachment "latencytraces-jack-idle.gz" of type "application/x-gzip" (27814 bytes)

Download attachment "latencytraces-jack-ams-japa.gz" of type "application/x-gzip" (14044 bytes)