Hi, Please refer to this patch https://lists.rtems.org/pipermail/devel/2020-August/061572.html for reviewing my code. This new patch has some indentation corrections and minor code fixes that I missed looking at earlier. The pull request remains the same and can be used too.
Thank you, Richi. On Sun, Aug 23, 2020 at 3:33 AM Richi Dubey <richidu...@gmail.com> wrote: > v1 should point to the link: > https://lists.rtems.org/pipermail/devel/2020-July/060645.html > > On Sun, Aug 23, 2020 at 3:27 AM Richi Dubey <richidu...@gmail.com> wrote: > >> Hi, >> >> I am really excited to annonunce the pre-release verion of Strong APA >> Scheduer for RTEMS that we've been working so hard for! >> >> The documentation for the scheduler is now live at : >> https://richidubey.github.io/Strong-APA-Documentation/html/ >> >> To understand how the code works, please go through these links (in >> order): >> >> Documentation for Struct defined for various uses >> <https://richidubey.github.io/Strong-APA-Documentation/html/structScheduler__strong__APA__Struct.html> >> Changes for Enqueue >> <https://rtemswithrichi.wordpress.com/scheduler-strong-apa-changes-scheduler_smp_enqueue/> >> Changes for Get_highest_ready >> <https://rtemswithrichi.wordpress.com/scheduler-strong-apa-changes-get_highest_ready/> >> >> Improvements over v1 >> <https://github.com/richidubey/rtems/blob/9bb37330e2c91a2fbd5bf3236770acb06d3466b3/cpukit/include/rtems/score/schedulersmpimpl.h#L1093> >> (after >> last <https://github.com/richidubey/rtems/pull/4> review): >> >> - Better coding style and variable naming >> - Better documentation >> - Successfully runs the Strong APA test >> <https://lists.rtems.org/pipermail/devel/2020-August/061474.html> >> >> Plans for v2: >> >> - Use chain of scheduled nodes present in SMP Context rather than per cpu >> variables based on this >> <https://lists.rtems.org/pipermail/devel/2020-August/061520.html> >> discussion >> - Work on the reviews >> >> I would request you to provide your reviews on whether the variables >> names that I chose makes sense (like the array Struct) and if my code >> follows the coding conventions. Also, please let me know if there's >> anything that's still looks wrong in the code. >> >> Please use this >> <https://lists.rtems.org/pipermail/devel/2020-August/061559.html> patch >> or this <https://github.com/richidubey/rtems/pull/7> pull request to >> checkout my changes. >> >> Thanks, >> Richi. >> >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
