Commit 942ff746 authored by Philippe Gerum's avatar Philippe Gerum
Browse files

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
Signed-off-by: default avatarPhilippe Gerum <>
parent d4857c1d
...@@ -63,7 +63,7 @@ static time_t start_time; ...@@ -63,7 +63,7 @@ static time_t start_time;
static unsigned int period_usecs = 1000; /* 1ms */ static unsigned int period_usecs = 1000; /* 1ms */
static int responder_priority = 99; static int responder_priority = 98;
static int responder_cpu = -1; static int responder_cpu = -1;
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment