---
name: "cyclicdeadline"
section: "8"
platform: "linux"
package: "rt-tests"
version: "2.11-1"
release: "Arch Linux 2026-11-01"
platforms: ["linux"]
url: "https://new.carta.tech/cyclicdeadline"
---

# cyclicdeadline(8)

This program is used to test the deadline scheduler (SCHED\_DEADLINE) using a cyclictest style program

\# SPDX-License-Identifier: GPL-2.0-only

## NAME

cyclicdeadline - This program is used to test the deadline scheduler (SCHED\_DEADLINE) using a cyclictest style program

## SYNOPSIS

**cyclicdeadline** \[-a \[CPUSET\]\] \[-D TIME\] \[-h\]  \[-i INTV\] \[--json FILENAME\] \[-s STEP\] \[-t NUM\] \[-q\]

## DESCRIPTION

**cyclicdeadline** is a cyclictest style program for testing the deadline scheduler

## OPTIONS

- **-a --affinity \[CPUSET\]**

  Comma / hypen separated list of CPUs to run deadline tasks on

- **-D --duration TIME**

  Specify a length for the test to run Append 'm', 'h', or 'd' to specify minutes, hours, or days

- **-h --help**

  Show this help menu

- **-i --interval INTV**

  The shortest deadline for the tasks in us. (default 1000us)

- **--json=FILENAME**

  Write final results into FILENAME, JSON formatted.

- **-s --step STEP**

  The amount to increase the deadline for each task in us. (default 500us)

- **-t --threads NUM**

  The number of threads to run as deadline (default 1)

- **-q, --quiet**

  Print a summary only on exit. Useful for automated tests, where only the summary output needs to be captured.

- **-b, --breaktrace=USEC**

  Send break trace command when latency \> USEC

- **--tracemark**

  write a trace mark when -b latency is exceeded.\

## AUTHOR

cyclicdeadline was written by Steven Rostedt \<rostedt@goodmis.org\>

This manual page was written by John Kacur \<jkacur@redhat.com\>