Optimizing ARM64 Atomics: When to Use Large System Extensions (LSE)
Learn how to leverage ARMv8.1-A Large System Extensions (LSE) to replace slow LL/SC atomic loops with high-performance hardware instructions in Linux.
Loading…
ReadMeFeed / Community knowledge
#atomics
Real questions. Useful conversations. Find the people who know your stack.
aarch64C11 Atomics: Lock-Free Shared State and Memory Ordering
C11 <stdatomic.h> provides standard atomic types and operations for thread-safe shared data. Learn how to use atomic counters and publication flags, choose correct memory orders, and verify lock-free support.
OpenCL global memory visibility limits across work-groups without fences
Goal I want a producer work-group to write a result buffer in global memory and have a consumer work-group read that data reliably within the same kernel launch, without stale reads. Constraints and uncertainty My understanding of the OpenCL C memory model is that it is relaxed: writes to global memory by one work-item are not guaranteed visible to others wi
opencl