7 May
2006
7 May
'06
1:44 p.m.
On Sun, 2006-05-07 at 16:16 +0100, Martin Habets wrote:
On Sat, May 06, 2006 at 10:13:42AM -0400, Lee Revell
wrote:
Yeah I was thinking about this. There are workloads that cause xruns
(like display activity with some video drivers) that are hard to
simulate this way. Maybe we could generate some load and tell the user
to generate their own load at the same time.
Lee
Same as the existing CLI tools - it would start
an RT thread that polls
on the RTC, then tell the user to generate some load (switch windows, do
a find /, pingflood the default gateway, whatever), then report back the
maximum latency.
In stead of telling the user to generate some (unpredictable) load I would
suggest re-using the parts from the alsa latency tester tool that automatically
spawn another process with a known load.