Lines Matching refs:rt

26  system behavior. As for -rt (group) scheduling, it is assumed that root users
228  to -deadline tasks is similar to the one already used for -rt
230  Documentation/scheduler/sched-rt-group.txt), and is based on readable/
238  is that -deadline tasks have bandwidth on their own (while -rt ones don't!),
253  For now the -rt knobs are used for -deadline admission control and the
254  -deadline runtime is accounted against the -rt runtime. We realise that this
257  run -rt tasks from a -deadline server; in which case the -rt bandwidth is a
316  follows (rt-app is used to create a -deadline task).
329  rt-app -t 100000:10000:d:0 -D5 (it is now actually superfluous to specify
358  The first testing application is called rt-app and can be used to
359  start multiple threads with specific parameters. rt-app supports
361  parameters (e.g., niceness, priority, runtime/deadline/period). rt-app
365  rt-app is available at: https://github.com/scheduler-tools/rt-app.
370   # rt-app -t 100000:10000:d -t 150000:20000:f:10 -D5
378  can be passed as input to rt-app with something like this:
380   # rt-app my_config.json
383  of the command line options. Please refer to rt-app documentation for more
384  details (<rt-app-sources>/doc/*.json).