1CYCLICDEADLINE(8)           System Manager's Manual          CYCLICDEADLINE(8)
2
3
4

NAME

6       cyclicdeadline  -  This  program is used to test the deadline scheduler
7       (SCHED_DEADLINE) using a cyclictest style program
8

SYNOPSIS

10       cyclicdeadline [-a [CPUSET]] [-D TIME] [-h]  [-i  INTV]  [--json  FILE‐
11       NAME] [-s STEP] [-t NUM] [-q]
12

DESCRIPTION

14       cyclicdeadline  is  a cyclictest style program for testing the deadline
15       scheduler
16

OPTIONS

18       -a --affinity [CPUSET]
19              Comma / hypen separated list of CPUs to run deadline tasks on
20
21       -D --duration TIME
22              Specify a length for the test to run Append 'm', 'h', or 'd'  to
23              specify minutes, hours, or days
24
25       -h --help
26              Show this help menu
27
28       -i --interval INTV
29              The shortest deadline for the tasks in us. (default 1000us)
30
31       --json=FILENAME
32              Write final results into FILENAME, JSON formatted.
33
34       -s --step STEP
35              The  amount  to  increase the deadline for each task in us. (de‐
36              fault 500us)
37
38       -t --threads NUM
39              The number of threads to run as deadline (default 1)
40
41       -q, --quiet
42              Print a summary only on exit. Useful for automated tests,  where
43              only the summary output needs to be captured.
44
45       -b, --breaktrace=USEC
46              Send break trace command when latency > USEC
47
48       --tracemark
49              write a trace mark when -b latency is exceeded.
50

AUTHOR

52       cyclicdeadline was written by Steven Rostedt <rostedt@goodmis.org>
53
54       This manual page was written by John Kacur <jkacur@redhat.com>
55
56
57
58                               January 16, 2020              CYCLICDEADLINE(8)