01.06.2014 Views

Concurrent Systems II - Bad Request - Trinity College Dublin

Concurrent Systems II - Bad Request - Trinity College Dublin

Concurrent Systems II - Bad Request - Trinity College Dublin

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Attempt #4<br />

• Attempt #3 fails because each process insisted on entering its<br />

critical region (by asserting its wait variable).<br />

◾Having insisted on entering, they could not proceed because they<br />

were waiting for all others to not be in their critical regions.<br />

• So, attempt #4 works by our process claiming to enter the<br />

critical region before checking it’s okay by everyone else.<br />

◾Then, if another process is in its critical region, our process<br />

relinquishes and reasserts its insistence on entering its critical<br />

region<br />

• i.e. Attempt #4 negates and then reasserts its wait variable.<br />

116<br />

<strong>Trinity</strong> <strong>College</strong> <strong>Dublin</strong><br />

© Mike Brady 2007–2009

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!