RT-MIGRATE-TEST(8)

πŸ“¦
version 2.11 Β· 2 versions
, in arch rolling, centos-stream 10, centos-stream 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu resolute, ubuntu stonking

🌸 RT-MIGRATE-TEST(8) β€” the real-time task migration program, bestie edition 🌸

okay so this is a page from the System Manager's Manual, and it's about a lil tool called rt-migrate-test. she's giving real-time multiprocessor scheduling energy and she's here to spill. grab a snack. πŸ“

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

✨ NAME ✨

rt-migrate-test β€” the real-time task migration program πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

rt-migrate-test [-c|--check] [-D|--duration TIME] [-e|--equal]
[-h|--help] [--json FILENAME] [-l|--loops LOOPS] [-m|--maxerr TIME]
[-p|--prio PRIO] [-r|--run-time TIME] [-s|--sleep-time TIME] [NR_TASKS]

like, that's the whole vibe right there. she takes options and optionally a number of tasks, that's it, that's the girl. ✨


πŸ‘‘ DESCRIPTION πŸ‘‘

so what she does is test real-time multiprocessor scheduling of tasks β€” the whole point is making sure the highest priority tasks are running on all available CPUs. no cap. if your RT tasks are out here getting ignored on some CPU while a lower-prio task is just vibing, this is the test that catches it. 😀


πŸ’– OPTIONS πŸ’–

she follows the usual GNU command line syntax, meaning long options start with two dashes (--). classic.

also, quick heads up bestie: in the summary of options below, a value in brackets () means that's the default value. so when you see (50) just know that's what you get if you don't say otherwise. iykyk. 🫢

  • -c, --check β€” stop the whole thing if a lower prio task ends up being quicker than a higher one (off by default). it's giving "we caught you slipping" energy.
  • -D, --duration=TIME β€” set a length for the test run. and here's the cute part: append m, h, or d to say minutes, hours, or days. so 30m is thirty minutes, periodt. ⏰
  • -e, --equal β€” use equal prio for #CPU-1 tasks. note she requires more than 2 CPUS for this one, so don't try it on a tiny machine, she will not be able to help you. πŸ™ˆ
  • -h, --help β€” display usage. the "just tell me what to do" option, iconic.
  • --json=FILENAME β€” write the final results into FILENAME, JSON formatted. for all my data girlies who want to parse it later. πŸ“Š
  • -l, --loops=LOOPS β€” number of iterations to run (50). she's gonna loop and loop and loop. πŸ”
  • -m, --maxerr=TIME β€” max allowed error, in microsecs. that's your tolerance threshold bestie, choose wisely.
  • -p, --prio=PRIO β€” base priority to start the RT tasks with (2). higher number, higher priority, main character energy. πŸ‘‘
  • -r, --run-time=TIME β€” run time (ms) to busy loop the threads (20). yes, busy loop, she's spinning, she's not sleeping, she's working. πŸ”₯
  • -s, --sleep-time=TIME β€” sleep time (ms) between intervals (100). the little nap she takes in between. 😴
  • [NR_TASKS] β€” number of tasks to run. default is number of cpus + 1, because one extra task keeps everybody honest fr fr. 🧚

🌈 AUTHOR 🌈

rt-migrate-test was written by Steven Rostedt <srostedt@redhat.com> πŸ’œ

this manual page was written by John Kacur <jkacur@redhat.com> πŸ’–


ok that's the whole page bestie, go run your scheduling tests and slay πŸ’…βœ¨

signing off from the System Manager's Manual β€” RT-MIGRATE-TEST(8), dated September 18, 2020. that's the source, that's the version tag, that's the date, all of it, no details dropped, we keep receipts around here. πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from