<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Are Lock-Free Concurrent Algorithms Practically Wait-Free? · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1311.3200/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1311.3200/feed.xml" rel="self" type="application/rss+xml" /><item><title>Are Lock-Free Concurrent Algorithms Practically Wait-Free? — mentioned by thmt</title><link>https://news.ycombinator.com/item?id=25492904</link><guid isPermaLink="false">urn:hackerpapers:mention:1311.3200:25492904</guid><pubDate>Mon, 21 Dec 2020 07:40:53 GMT</pubDate><description>&lt;p&gt;Alistarh et al. (https://arxiv.org/abs/1311.3200) show that assuming we have a kinder, non-malicious scheduler, the situation looks even better: lock-free (some process can make progress) algorithms have a stronger progress property of being wait-free (every process can make progress). As omazurov mentioned as a top-level comment, threads can also die, which is rather like never being scheduled. In practice, I suspect that you&amp;#x27;re right that it&amp;#x27;s often too extreme of a model—many programs use locks and don&amp;#x27;t worry too much about this issue.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1311.3200/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
