Test and test-and-set: Difference between revisions

Revision as of 14:57, 9 April 2023

Revision as of 15:01, 9 April 2023

Line 32:

==Caveat==

Although this [[Optimization (computer science)|optimization]] is useful in [[system programming]], test-and-set is to be avoided in high-level [[concurrent programming]]: spinning in applications derivesdeprives the operating system scheduler

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 spinning unproductively, waiting for threads that are not scheduled.