benchmarks/latmus: settle on SCHED_FIFO,98 for the responder thread
Using [SCHED_FIFO, 98] for running the responder thread will work for both EVL and native preemption configurations (i.e. GPIO mode). On the latter, it won't compete with high-priority housekeeping threads running in kernel space (prio 99) which is recommended and saner. On both, this leaves lower priority levels for common application-level threads. Signed-off-by: Philippe Gerum <rpm@xenomai.org>
This commit is contained in:
parent
d4857c1db0
commit
942ff7464f
|
@ -63,7 +63,7 @@ static time_t start_time;
|
|||
|
||||
static unsigned int period_usecs = 1000; /* 1ms */
|
||||
|
||||
static int responder_priority = 99;
|
||||
static int responder_priority = 98;
|
||||
|
||||
static int responder_cpu = -1;
|
||||
|
||||
|
|
Loading…
Reference in New Issue