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)
A clear case of writing that does not try to do too much in one post, and a look at discoverprofessionalgrowth maintained the same scoped discipline, posts that try to cover too much end up covering nothing well and this site has clearly chosen scope discipline as a core editorial principle which shows up clearly in what I read.
Speaking as someone who used to recommend blogs frequently and got out of the habit this site is rekindling that impulse, and a look at modernretailbuyinghub extended the rekindling, the recovery of an old habit triggered by encountering work that justifies it is itself a small kind of pleasure and this site is providing that recovery experience.
Really grateful for content like this, it does not waste my time and it does not insult my intelligence either, and a quick look at flexibleshoppingoutlet was the same, balanced respectful writing that makes a person feel welcome rather than rushed through pages of forced engagement just to keep clicking around.
A piece that handled the topic with appropriate weight without becoming portentous, and a look at modernretailbuyinghub continued that calibrated seriousness, content that takes itself seriously without becoming pompous is something this site has clearly figured out and the balance shows up in every piece I have read across multiple sessions now.