From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Lock-Free stack in Ada SPARK Date: Mon, 13 Feb 2017 09:22:22 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <26f24676-deab-48bc-b180-87d202877053@googlegroups.com> NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:33345 Date: 2017-02-13T09:22:22+01:00 List-Id: On 12/02/2017 23:25, Robert Eachus wrote: > I see some dangerous thinking going on here. [...] Why? Actually when cores are cheap lock-free approach becomes preferable or the only way, e.g. in the case of a distributed system. Regarding locks priorities, yes, it is IMO the easiest approach to prevent deadlocks, but it also introduces a danger of priority inversion. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de