Motion Master 6.0.0-alpha.86
Next-generation motion control software
Loading...
Searching...
No Matches
GameLoopConfig Struct Reference

"gameLoop" block — the real-time cyclic loop. More...

#include <config.h>

Public Attributes

uint32_t periodUs = 1000
 
int cpuAffinity = -1
 

Detailed Description

"gameLoop" block — the real-time cyclic loop.

Member Data Documentation

◆ cpuAffinity

int GameLoopConfig::cpuAffinity = -1

Core to pin the real-time thread to; -1 (the default) leaves it unpinned. Linux only. Set this to a core the kernel booted with isolcpus: such a core is removed from the scheduler and runs nothing unless a thread asks for it by name, so an isolated core is wasted until this is set. Only the RT thread moves — the HTTP, WebSocket, monitoring and refresher threads stay on the housekeeping cores, which is the difference between this and pinning the whole process with taskset or systemd's CPUAffinity=. Unlike periodUs this is fixed at startup: it describes the deployment, not something to retune live. Must name a core that exists.

◆ periodUs

uint32_t GameLoopConfig::periodUs = 1000

Cyclic timer period in microseconds (must be > 0). 1000 = 1 ms.


The documentation for this struct was generated from the following file: