Skip to content

Comment on An Introduction to Lock-Free Programmingparent

Comments

Based on your comment, I should probably be more precise and say: "the possibility of 'locking up' the entire application in some way". I'll update the post. There's nothing about this definition that prohibits a single thread from starving.

I think it's easier to phrase it in the positive sense: at least one thread is always making progress towards completion.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.