Rest of these patches looked good other than my few notes. Just another question, does this scheduler support: * partitioned EDF * clustered EDF * global EDF Just based on how the scheduler instances and affinity sets are defined?
On Fri, Jul 7, 2017 at 9:54 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > The EDF SMP scheduler supports simple thread processor affinities > (see #3059) with a small run-time overhead. The current default SMP > scheduler lacks support for thread processor affinities at all. The EDF > SMP scheduler offers a good feature set for most applications. So, use > it by default. Run-time libraries like libgomp, MTAPI, work stealing > schedulers, language interpreters (e.g. Erlang virtual machine), > maintainence of per-processor data (e.g. Universal Memory Allocator > (UMA)), etc. use a one-to-one thread processor affinity for example. > > Update #3063. > --- > cpukit/sapi/include/confdefs.h | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/cpukit/sapi/include/confdefs.h b/cpukit/sapi/include/confdefs.h > index d01c927014..50e04b23cb 100755 > --- a/cpukit/sapi/include/confdefs.h > +++ b/cpukit/sapi/include/confdefs.h > @@ -811,9 +811,9 @@ extern rtems_initialization_tasks_table > Initialization_tasks[]; > #if defined(RTEMS_SMP) && CONFIGURE_MAXIMUM_PROCESSORS > 1 > /** > * If no scheduler is specified in an SMP configuration, the > - * priority scheduler is default. > + * EDF scheduler is default. > */ > - #define CONFIGURE_SCHEDULER_PRIORITY_SMP > + #define CONFIGURE_SCHEDULER_EDF_SMP > #else > /** > * If no scheduler is specified in a uniprocessor configuration, the > -- > 2.12.3 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel