<div dir="ltr">Hi,<div><br></div><div>Can someone please help me understand how this (<a href="https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c#n385">https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c#n385</a>) if condition works. Why are we removing the ready queue Node from the chain of Affine queues when we are allocating a different processor (<a href="https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c#n398">https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c#n398</a>) to the node which was currently scheduled on the CPU of that (the ready queue mentioned in the if condition's) ready queue? </div><div><br></div><div>Thanks,<br></div><div>Richi.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 13, 2020 at 4:57 PM Richi Dubey <<a href="mailto:richidubey@gmail.com">richidubey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>We use a zero-length <a href="https://git.rtems.org/rtems/tree/cpukit/include/rtems/score/scheduleredfsmp.h#n105" target="_blank">array</a> in the definition of <span style="color:rgb(0,0,0);font-size:13.3333px">Scheduler_EDF_SMP_Context, but I can not see any code in scheduleredfsmp.c (</span><a href="https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c" target="_blank">https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c</a>) which actually increases the size of the array. All I can see is code that access/manipulate the array elements, but I do not see any code which does malloc/adds <span style="color:rgb(0,0,0);font-size:13.3333px">Scheduler_EDF_SMP_Ready_queue elements to the array.</span></div><div><br></div><div>Can someone please help me understand this.</div><div><br></div><div>Thanks,</div><div>Richi. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 12, 2020 at 12:49 PM Richi Dubey <<a href="mailto:richidubey@gmail.com" target="_blank">richidubey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I understand now. Thank you.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 11, 2020 at 7:35 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Jul 11, 2020 at 12:31 AM Richi Dubey <<a href="mailto:richidubey@gmail.com" target="_blank">richidubey@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I noticed that we have defined all the scheduler non entry-point functions in <a href="https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c" rel="noreferrer" target="_blank">https://git.rtems.org/rtems/tree/cpukit/score/src/scheduleredfsmp.c</a> as static inline, which makes them invisible inside the doxygen comments (<a href="https://docs.rtems.org/doxygen/branches/master/scheduleredfsmp_8c.html" rel="noreferrer" target="_blank">https://docs.rtems.org/doxygen/branches/master/scheduleredfsmp_8c.html</a>).<br>
><br>
> Is there any reason why we choose to do so?<br>
><br>
<br>
Encapsulation / method hiding. It is normal to define and document<br>
interfaces moreso than implementations.<br>
<br>
> Thanks,<br>
> Richi.<br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>