News for hackers. Stuff that matters.
Re:Lock-Free Rust: Crossbeam in 2019 by dagenix on Wednesday January 30, 2019 @06:59PM (#19040947)
I don't think that is quite correct. By that definition, any alhorithm that is free of deadlocks would be a lock free algorithm. But, I'm fairly sure that isn't the case - otherwise a hashmap protected by a single mutex would be considered a lock free data structure since as there is only a single mutex, deadlock would be impossible.

I think the key paragraph from the Wikipedia article is:

"In particular, if one thread is suspended, then a lock-free algorithm guarantees that the remaining threads can still make progress. Hence, if two threads can contend for the same mutex lock or spinlock, then the algorithm is not lock-free. (If we suspend one thread that holds the lock, then the second thread will block.)"

Re:Lock-Free Rust: Crossbeam in 2019 by elteto on Thursday January 31, 2019 @06:32PM (#19050130)
Yes, you are correct. I missed the "some thread must always be able to make progress regardless of the state of the other threads".