Deutsch English Français Italiano |
<vb51mr$2v0pc$2@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news.in-chemnitz.de!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> Newsgroups: comp.arch Subject: Re: arm ldxr/stxr vs cas Date: Mon, 2 Sep 2024 11:55:23 -0700 Organization: A noiseless patient Spider Lines: 15 Message-ID: <vb51mr$2v0pc$2@dont-email.me> References: <vb4sit$2u7e2$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 02 Sep 2024 20:55:24 +0200 (CEST) Injection-Info: dont-email.me; posting-host="37ad5ea9d8adc5b106b971373399347c"; logging-data="3113772"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX193CCkFq77c7KZA1Z0ctYMVO/ZCclgvg4Y=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:7lDtD8NyNjW2rWd338gh2zMLlNM= Content-Language: en-US In-Reply-To: <vb4sit$2u7e2$1@dont-email.me> Bytes: 1777 On 9/2/2024 10:27 AM, jseigh wrote: > I read that arm added the cas instruction because they didn't think > ldxr/stxr would scale well. It wasn't clear to me as to why that > would be the case. I would think the memory lock mechanism would > have really low overhead vs cas having to do an interlocked load > and store. Unless maybe the memory lock size might be large > enough to cause false sharing issues. Any ideas? Reservation granularity? Wrt the PPC, wow this an older thread: https://groups.google.com/g/comp.arch/c/yREvvvKvr6k/m/nRZ5tpLwDNQJ LL/SC can spuriously fail... It's more obstruction free than lock-free? I think this is why a strong and weak CAS are in the C/C++ std's?