CYCLICDEADLINE(8)

💖 CYCLICDEADLINE 💖

okay bestie, welcome to cyclicdeadline(8) from the System Manager's Manual — she's a deadline-scheduler stress-tester and she's serving. Also real quick, before we even start: this page carries the license line # SPDX-License-Identifier: GPL-2.0-only, so jot that down, it's important, we don't erase receipts around here 💅

✨ NAME ✨

cyclicdeadline — this program is used to test the deadline scheduler (SCHED_DEADLINE) using a cyclictest style program. no cap, that's literally her whole job description 🎀

🦋 SYNOPSIS 🦋

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

look at that little command line. iconic. so many brackets. so many options. she's flexible, she's booked, she's thriving ✨

🌸 DESCRIPTION 🌸

so like, cyclicdeadline is a cyclictest style program for testing the deadline scheduler. that's it. that's the vibe. it pokes at SCHED_DEADLINE and tells you what happened 🧚

👑 OPTIONS 👑

• -a, --affinity [CPUSET] — a comma / hyphen separated list of CPUs to run your deadline tasks on. you're basically picking which CPUs get invited to the party 🎉
• -D, --duration TIME — say how long the test should run. you can tack 'm', 'h', or 'd' onto it to mean minutes, hours, or days. yes, days. she can go the distance 🫶
• -h, --help — show this help menu. the classic. the comfort option 🥰
• -i, --interval INTV — the shortest deadline for the tasks, in us. (default 1000us) ⏱️
• --json=FILENAME — write the final results into FILENAME, JSON formatted. for when you want your numbers in a cute structured little outfit 💖
• -s, --step STEP — how much 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. super useful for automated tests, where only the summary output needs to be captured. she's lowkey but she still shows up at the end 💅
• -b, --breaktrace=USEC — send break trace command when latency > USEC. like a lil alarm bell going off 🔔
• --tracemark — write a trace mark when -b latency is exceeded. leave a lil sticky note so you know where it went down 📝

💜 AUTHOR 💜

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

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

and that's the whole page, bestie 🌈 huge shoutout to the System Manager's Manual for hosting her, and this gorgeous document is dated January 16, 2020 — so when you see CYCLICDEADLINE(8) floating around in the wild, that's her, that's the girl, go read her again fr fr 💀✨🎀