Sujet : Re: arm ldxr/stxr vs cas
De : jseigh_es00 (at) *nospam* xemaps.com (jseigh)
Groupes : comp.archDate : 02. Sep 2024, 20:59:36
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vb55f8$2vfl7$1@dont-email.me>
References : 1 2 3
User-Agent : Mozilla Thunderbird
On 9/2/24 14:58, Chris M. Thomasson wrote:
On 9/2/2024 11:55 AM, Chris M. Thomasson wrote:
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?
>
Btw, have you talked with Alexander Terekhov lately? He is a smart guy. :^)
What, where? c.p.t. is gone. It's crickets everywhere else.
arm ldxr/stxr vs cas
Re: arm ldxr/stxr vs cas