From 2035544754c3dd69570b204d774dcd4c7284750c Mon Sep 17 00:00:00 2001 From: Jeremy Erickson Date: Mon, 28 May 2012 13:24:37 -0400 Subject: Add a comment on how G-EDF splitting works --- litmus/sched_gsn_edf_split.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/litmus/sched_gsn_edf_split.c b/litmus/sched_gsn_edf_split.c index 0fe324e2c156..bcad03fd2c9b 100644 --- a/litmus/sched_gsn_edf_split.c +++ b/litmus/sched_gsn_edf_split.c @@ -6,6 +6,18 @@ * * This plugin is a modified version of the prior GSN-EDF plugin in * litmus/sched_gsn_edf_split.c + * + * Splitting an implicit-deadline job simply means splitting each job into an + * integral number of subjobs. For example, a task with a period of 10 ms and + * a runtime of 4 ms could be re-organized as a task with a period of 5 ms and + * a runtime of 2 ms, with analytical benefit for bounded tardiness (ignoring + * overheads and assuming no critical sections). + * + * Because our analysis works with early releasing, we actually only release + * each job once, but move the subjob deadline back when the appropriate amount + * of execution has been completed. (In the example above, a job released at + * time 0 would intially have a subjob deadline at time 5, but this deadline + * would be moved to time 10 as soon as 2 ms of execution had completed.) */ #include -- cgit v1.2.2