Exercise 1
Idle-waiting Thread Joining
– It have as an objective to change the method “join” of a Thread. It was implemented like this:
[code lang=”c”] while(_state != FINISHING)
yield();
[/code]
This method consist in verify the state of the Thread that is joined, if the state is different from FINISHING, it calls yield(). This solution cause an overhead, because it do this verification all the time that the process is Phased. We should implement a new function, that don`t cause this overhead.
Modified files:
– thread.cc
– Thread.h
EPOS with our solution.
Steps, and explanation about other solutions (PORTUGUESE)
Definitely returning here, that is decided, and a look at buildfuturefocusedpaths only made the case stronger, this is one of those rare websites that rewards regular visits rather than feeling stale after the first read which is something I cannot say about most of the places I bookmark today across all my topics.
Coming back to this one, definitely, and a quick visit to longtermvaluealliances only made me more sure of that, the kind of writing that makes you want to set aside time later rather than rushing through it now while distracted by everything else competing for attention on the screen today across so many tabs.
Appreciate how nothing here feels copied or pieced together from other places, the voice is consistent and the tone stays human, and after I checked simpleecommercesolutions I noticed the same style holds, which is a small detail but it makes the whole experience feel personal rather than like another generic site.
Really appreciate that the writer did not assume I would read every other related post first, and a look at discoverbetterapproaches kept that self contained feel going where each piece can stand alone, accessibility for new readers is a sign of generous editorial thinking and this site has clearly invested in that approach.