Revision as of 17:38, 19 March 2023 edit Znok (talk \| contribs) 32 edits Poignancy, explanation of underlying mechanisms ← Previous edit		Revision as of 17:40, 19 March 2023 edit undo Znok (talk \| contribs) 32 edits m editorial Next edit →
Line 35: the knowledge of who is blocking on what. Consequently, the scheduler will have to guess on how to allocate CPU time among the threads -- typically just allowing the threads to use up their timing quota. Threads will end up burning CPU cycles spinning, waiting for threads that are not scheduled. By using operating-system provided lock objects, such as mutexes, the OS can schedule exactly ~~those~~the unblocked threads ~~ready to run~~. ==See also==

Test and test-and-set: Difference between revisions