1CYCLICDEADLINE(8)           System Manager's Manual          CYCLICDEADLINE(8)
2
3
4
5# SPDX-License-Identifier: GPL-2.0-only
6

NAME

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

SYNOPSIS

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

DESCRIPTION

16       cyclicdeadline  is  a cyclictest style program for testing the deadline
17       scheduler
18

OPTIONS

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

AUTHOR

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