rk_stubby man page
SYNOPSIS
rk_stubby options
DESCRIPTION
The rk_stubby utility is used to test the rk_stub simula-
tor library.
Available options:
-name of-resource-set
Set the name of the resource set that is created.
This value is then used to determine the names of
the input and output files. Default: test
-verbosity <0-1>
Set the verbosity level, where zero means no output
and higher levels will reveal more and more debug-
ging information. Default: 0
-compute_sec secs
Set the number of seconds of computation time.
Default: 1
-compute_ns ns
Set the number of nanoseconds of computation time.
Default: 0
-period_sec secs
Set the number of seconds in the period. Default:
2
-period_ns ns
Set the number of nanoseconds in the period.
Default: 0
-deadline_sec secs
Set the number of seconds in the deadline, which is
relative to the start of the period. Default: 2
-deadline_ns ns
Set the number of nanoseconds in the deadline,
which is relative to the start of the period.
Default: 0
-for secs
Specify the number of seconds to run the test for.
Default: 4
-drop_all bool
Switch that determines whether or not the delegate
will drop all the simulated data to be processed.
This switch is really only meant as a sanity check
for the drop code. Default: false
-drop_behind bool
Switch that determines whether or not the delegate
will drop data when processing is falling behind.
Default: false
EXAMPLES
To simulate a process with a period of 1 second, deadline
of 500000000 nanos, and a compute time of 250000000 nanos.
rk_stubby -period_sec 1 -deadline_sec 0 -dead-
line_ns 500000000 -compute_sec 0 -compute_ns
250000000
RETURN VALUES
0 The simulation completed successfully.
1 The simulation failed for one reason or another.
INPUT FILES
<resource-set-name>_cpu_times
The simulator input file that contains the required
CPU percentages. The contents of the file should
be a whitespace separated list of floats that spec-
ify the percentage of CPU time required by the pro-
cess for a repeating sequence of periods. For
example, the times file for a resource set named
"steady_50" that required 50% of the CPU at every
period would be named "steady_50_cpu_times" and
contain only "50.0". Another, more complex exam-
ple, would be a reserve that oscillated between 10%
and 50% with 10% steps would contain "10.0 20.0
30.0 40.0 50.0 40.0 30.0 20.0 10.0".
OUTPUT FILES
rk.log A log of the calls into the rk_stub simulator.
The output of CPU simulation is a set of files that can be
fed into gnuplot. The contents of the file are two
columns of numbers, a time value, and a CPU percentage or
an arbitrary value that marks some event. The current
list of files is:
<resource-set-name>_cpu_period
The CPU reserve's period.
<resource-set-name>_cpu_deadline
The CPU reserve's deadlines.
<resource-set-name>_cpu_complete
Marks the completion of a data period.
<resource-set-name>_cpu_drop
Marks a data period as being dropped.
<resource-set-name>_cpu_realtime
The CPU time required by the process.
<resource-set-name>_cpu_success
The actual CPU time received by a process that is
making its deadlines.
<resource-set-name>_cpu_fail
The actual CPU time received by a process that is
missing its deadlines.
SEE ALSO
gnuplot(1)
NOTES
The Alchemy project can be found on the web at
http://www.cs.utah.edu/flux/alchemy
AUTHOR
The Alchemy project at the University of Utah.
CPU Broker 0.5 2003/09/02 16:32:15 RK_STUBBY(1)
Man(1) output converted with
man2html