• 0

[Concurrent Programming] "passing the condition"


Question

Howdy,

Anybody out there know what the term "passing the condition" means? I'm just a little confused about it all and an elaboration on the idea behind would be good. In particular, here's the pseudo code we've been studying that revolves around it. It's based on the Shortest-Job-Next Allocation problem.

monitor SJN {

 ?bool free = true; # invariant: turn ordered by time && (free -> turn is empty)
 ?condition_variable turn; # signaled when resource available

 ?# request the resource
 ?procedure request(int time) {
 ? ?if (free)
 ? ? ?free = false;
 ? ?else
 ? ? ?wait(turn, time);
 ?}

 ?# release the resource
 ?procedure release() {
 ? ?if(empty(turn)) # are there processes waiting on the CV 'turn'?
 ? ? ?free = true;
 ? ?else
 ? ? ?signal(turn);
 ?}

}

I'm confused about this because consider the case where we're done usingrelease()d decide to release() it.

If there are no proceempty()n the CV (ie.true will return true and the if block will be executed), then we set:

free = true;

Then we don't need to signal. That makes sense.

But coare case where there are processes blocked on the CV?! (ie. those processes are sleeping waiting for it and need to be woken up by the process finishing with the rsignal(turn) calling <empty()).

Well, empty() would return false and the else block would be executed. Here the code says:

signal(turn);

But we haven't reset free yet? So how could another process request the resource and successfully get it? Won't it just be put to sleewait()it'll call wait())since free is still false?

Any clarification would be great.

Edited by fault

4 answers to this question

Recommended Posts

  • 0

If process B calls request(), and free = false, then it will call wait(). Say process A was using the resource and is now done. It calls signal(). I'm assuming this call will wake up process B, and B will start executing after wait(), and completely avoid the free check.

In short, any new processes are just going to wait() until until free = true. When a process is done with a resource, it checks to see if anyone is waiting. If they are, it wakes them up; the resource would be "switched", so it would wrong to set free = true. On the other hand, if no processes are waiting, then free = true is correct.

There are a few races conditions in the code, but I don't know the context/assumptions this code is running under.

  • 0
  Andareed said:
There are a few races conditions in the code, but I don't know the context/assumptions this code is running under.

586424643[/snapback]

yes

and it something belong to OS, with more Complex condition than this.

  • 0
  Andareed said:
If process B calls request(), and free = false, then it will call wait(). Say process A was using the resource and is now done. It calls signal(). I'm assuming this call will wake up process B, and B will start executing after wait(), and completely avoid the free check.

586424643[/snapback]

Ohhh, god damn - that's so obvious, how did I miss that? :pinch: Makes perfect sense. Cheers.
  Andareed said:
In short, any new processes are just going to wait() until until free = true. When a process is done with a resource, it checks to see if anyone is waiting. If they are, it wakes them up; the resource would be "switched", so it would wrong to set free = true. On the other hand, if no processes are waiting, then free = true is correct.

586424643[/snapback]

Ah, I see - hence the term "passing the condition"... it's all clear now.
  Andareed said:
There are a few races conditions in the code, but I don't know the context/assumptions this code is running under.

586424643[/snapback]

There are? Where! :wacko:

Another question, is "passing the baton" the same as "passing the condition"? Cheers.

  • 0

Suppose process A and B both call request (while it is free). It's possible (due to pre-emptive context switching), that A will execute "if (free)" (which evaluates to true), and then is pre-empted by B. Then B runs, and also executes "if (free)", and then "free = false;". B will claim it owns the condition. Now say B is pre-empted, and A runs. A will run execute "free = false" too, and will also claim that it owns the condition.

There's a similar issue when calling empty().

If you aren't dealing pre-emptive scheduling (i.e., a thread runs until it calls a function that blocks, e.g., wait()), then there is no race condition.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Seem like they are seeking for a one size fits all. You have power users and "what's a computer" generation growing up on phones, tablets, and Chromebooks.
    • Guessing it was profitable enough inserting prompted apps vs the hate it generated.
    • Also good for Debugging or troubleshooting your game.. i dont get it why nvidia app or amd does not show this data.. if steam can do it..
    • Microsoft reportedly planning to lay off thousands of employees, mostly in sales by Usama Jawad Back in May 2025, Microsoft decided to lay off 3% of its workforce, which amounted to roughly 6,000 employees. It claimed that this decision allowed it to implement better organizational changes in a "dynamic marketplace". Now, a new report claims that the Redmond tech firm is planning to lay off thousands more next month. Citing unnamed sources, Bloomberg reports that as the company continues investing heavily in its AI ventures, it is about to announce layoffs of thousands of workers as early as next month. This reduction in workforce will primarily affect sales teams, but they won't be the only ones affected. That said, the sources did mention that the timing for this announcement may change. This move, if true, won't be entirely surprising. In April 2025, Microsoft announced that it will be relying more on third-party firms to sell its software to small- and medium-sized customers. It's currently unclear how many employees will be impacted by this change, but even if the layoff percentage is in the single digits, it would still be significant as it would be impacting the professional careers of thousands. The May 2025 layoffs primarily impacted engineering and product teams. The other major round of layoffs prior to this was the decision to eliminate 10,000 jobs back in January 2023. Those represented 5% of the total workforce at that time, with numerous teams, including the one leading Mixed Reality (MR) efforts, being heavily impacted. It is interesting to note that if the timing of the announcement for layoffs is accurate, it would be soon after Microsoft closes its fiscal year at the end of June 2025. Although we'll get financial reports for the latest quarter soon after too, one has to wonder what the human cost of profit is, as Microsoft continues to report billions of dollars in revenue every quarter. Source: Bloomberg (paywall)
  • Recent Achievements

    • First Post
      Fuzz_c earned a badge
      First Post
    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      704
    2. 2
      ATLien_0
      285
    3. 3
      Michael Scrip
      214
    4. 4
      +FloatingFatMan
      194
    5. 5
      Steven P.
      131
  • Tell a friend

    Love Neowin? Tell a friend!