The part 3 corresponding to the backtracking changes the filter_node pointer (the original node pointer passed to the function) and calls the Scheduler_SMP_Preempt, all of which is documented in the blog post. I feel like this might mean that the file is taking a higher-level role that it is supposed to and I cannot progress further without your views on this.
On Thu, Aug 6, 2020 at 8:45 PM Richi Dubey <richidu...@gmail.com> wrote: > Hi, > > Please find the blog post- > https://rtemswithrichi.wordpress.com/strong-apa-low-level-design-in-rtems/ > that > explains the low-level design for get_lowest_function, importance of which > was explained in the earlier high-level design description mail > <https://lists.rtems.org/pipermail/devel/2020-August/061120.html>. > > I really need your help in figuring out part 3 of the explanation > corresponding to backtracking part of the algorithm in the blog post. > > If it helps, Please find the latest pull request here > <https://github.com/richidubey/rtems/pull/6> and the edited files > schedulerstrongapa.c > <https://github.com/richidubey/rtems/blob/Strong-APA-v1.2/cpukit/score/src/schedulerstrongapa.c>, > schedulerstrongapa.h > <https://github.com/richidubey/rtems/blob/Strong-APA-v1.2/cpukit/include/rtems/score/schedulerstrongapa.h> > and scheduler.h > <https://github.com/richidubey/rtems/blob/Strong-APA-v1.2/cpukit/include/rtems/scheduler.h> > . > > Thanks! > Richi. >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
