Skip to content

Ex 1 – Dedicated Operating Systems – INE5424 – UFSC

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)

8,705 Comments

  1. Even just sampling a few posts the consistency is what stands out, and a look at clicktofindsolutions confirmed the broader pattern, sites where every piece I sample lives up to the standard set by the others are sites with serious quality control and this one has clearly invested in whatever editorial process produces that consistency reliably.

  2. Thanks for the practical examples scattered through the post rather than abstract theory only, and a look at learnandgrowprofessionally continued that grounded style, abstract points are easier to remember when paired with concrete situations and the writers here clearly understand how readers actually retain information from blog content reading sessions.

  3. Can I simply say what a relief to discover an individual who genuinely knows what they are discussing on the internet. You actually realize how to bring an issue to light and make it important. More and more people need to read this and understand this side of your story. I can’t believe you’re not more popular given that you definitely possess the gift.

Leave a Reply

Your email address will not be published. Required fields are marked *