Changes between Version 12 and Version 13 of scheduler

Timestamp:

Oct 6, 2018, 7:53:16 PM (6 years ago)

Author:

alain

Comment:

--

scheduler

@@ -5 +5 @@
 == A) General principles ==
 
-There is one private scheduler per core, and ALMOS-MKH does not support thread migration: threads are assigned to a given core at thread creation, and will never be executed by another core, until thread destruction.
-ALMOS-MKH implement a preemptive policy for time sharing between all threads assigned to given core. The <cpu_context> and <fpu_context> fields in the thread descriptor define the storage required to save (or initialize) the core registers values when the thread is not running. A fixed number of TICK periods - called quantum - is allocated to a running thread. 
+Our main goal is to avoid to remove all contention points in the kernel. Therefore, we choose a fully distributed approach: There is one private scheduler per core, and ALMOS-MKH does not support thread migration: threads are assigned to a given core at thread creation, and will never be executed by another core, until thread destruction.
+ALMOS-MKH implement a preemptive policy for time sharing between all threads assigned to a given core. The <cpu_context> and <fpu_context> fields in the thread descriptor define the storage required to save (or initialize) the core registers values when the thread is not running. A fixed number of TICK periods - called quantum - is allocated to a running thread. 
  * The value of the TICK period (in milli-second) is defined by the CONFIG_SCHED_TICK_MS_PERIOD parameter. 
  * The number of TICKS  is defined by the CONFIG_SCHED_TICKS_PER_QUANTUM configuration parameter.