TechQA.

Question

Why is the standard C# event invocation pattern thread-safe without a memory barrier or cache invalidation? What about similar code?

score 880 · Answer 1 · 2015-06-10 14:48:37

5

Answer

880

Views

Why is the standard C# event invocation pattern thread-safe without a memory barrier or cache invalidation? What about similar code?

880 views Asked by Andrew Russell At 10 June 2015 at 14:48

score 699 · Answer 2 · 2015-06-20 07:57:23

Does C++11 guarantee memory ordering between a release fence and a consume operation?

699 views Asked by Edmund At 20 June 2015 at 07:57

score 4454 · Answer 3 · 2015-06-20 20:05:09

Memory barriers force cache coherency?

4.4k views Asked by Wad At 20 June 2015 at 20:05

score 213 · Answer 4 · 2015-06-21 09:33:57

Spin locked stack and memory barriers (C++)

213 views Asked by sribin At 21 June 2015 at 09:33

score 526 · Answer 5 · 2016-12-22 22:24:21

Lock-free stack: visibility issue when checking hazard pointers during pop()?

526 views Asked by Enrico M. Crisostomo At 22 December 2016 at 22:24

score 364 · Answer 6 · 2016-12-27 07:33:02

Is deadlock possible in this simple scenario?

364 views Asked by Junekey Jeon At 27 December 2016 at 07:33

score 348 · Answer 7 · 2017-01-02 12:58:05

Are memory fences required here?

348 views Asked by Bernard At 02 January 2017 at 12:58

score 450 · Answer 8 · 2017-01-01 21:39:39

lock-free synchronization, fences and memory order (store operation with acquire semantics)

450 views Asked by Ferenc At 01 January 2017 at 21:39

score 179 · Answer 9 · 2014-11-10 21:38:26

C Variable Not Updating on Thread Iteration

179 views Asked by Johnny Thompson At 10 November 2014 at 21:38

score 796 · Answer 10 · 2024-11-25 01:41:25

Do I need to use volatile keyword for memory access in critical section?

796 views Asked by Robotbugs At 25 November 2024 at 01:41

TechQA.

List Question

Why is the standard C# event invocation pattern thread-safe without a memory barrier or cache invalidation? What about similar code?

Does C++11 guarantee memory ordering between a release fence and a consume operation?

Memory barriers force cache coherency?

Spin locked stack and memory barriers (C++)

Lock-free stack: visibility issue when checking hazard pointers during pop()?

Is deadlock possible in this simple scenario?

Are memory fences required here?

lock-free synchronization, fences and memory order (store operation with acquire semantics)

C Variable Not Updating on Thread Iteration

Do I need to use volatile keyword for memory access in critical section?

Popular Questions

Popular Tags

Trending Questions