EDF schedulers: Support early job releasing.

This patch allows a task to request early releasing
via rt_task parameters to sys_set_task_rt_param().
Note that early releasing can easily peg your CPUs
since early-releasing tasks never suspend to wait for
their next job. As such, early releasing is really
only useful in the context of implementing bandwidth
servers, interrupt handling threads (or any thread that
spends most of its time waiting for an event), or
short-lived computations. If early releasing pegs your
CPUs, then you probably shouldn't be using it.

1 files changed, 21 insertions, 0 deletions

diff --git a/litmus/Kconfig b/litmus/Kconfig
index bd6635c8de08..795fbe1a769e 100644
--- a/litmus/Kconfig
+++ b/litmus/Kconfig
@@ -79,6 +79,27 @@ config SCHED_CPU_AFFINITY
 
           Say Yes if unsure.
 
+config ALLOW_EARLY_RELEASE
+        bool "Allow Early Releasing"
+        default y
+        help
+          Allow tasks to release jobs early (while still maintaining job
+          precedence constraints). Only supported by EDF schedulers. Early
+          releasing must be explicitly requested by real-time tasks via
+          the task_params passed to sys_set_task_rt_param().
+
+          Early releasing can improve job response times while maintaining
+          real-time correctness. However, it can easily peg your CPUs
+          since tasks never suspend to wait for their next job. As such, early
+          releasing is really only useful in the context of implementing
+          bandwidth servers, interrupt handling threads, or short-lived
+          computations.
+
+          Beware that early releasing may affect real-time analysis
+          if using locking protocols or I/O.
+
+          Say Yes if unsure.
+
 choice
         prompt "EDF Tie-Break Behavior"
         default EDF_TIE_BREAK_LATENESS_NORM