Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #5099 > unrolled thread
| Started by | Horizon68 <horizon@horizon.com> |
|---|---|
| First post | 2019-07-15 10:42 -0700 |
| Last post | 2019-07-15 10:42 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.programming.threads
x86 Reordering Horizon68 <horizon@horizon.com> - 2019-07-15 10:42 -0700
| From | Horizon68 <horizon@horizon.com> |
|---|---|
| Date | 2019-07-15 10:42 -0700 |
| Subject | x86 Reordering |
| Message-ID | <qgidv4$qdd$5@dont-email.me> |
Hello.. x86 Reordering All modern x86 chips from Intel and AMD aggressively reorder instructions across a window which is around 200 instructions deep on recent CPUs from both manufacturers (i.e. a new instruction may execute while an older instruction more than 200 instructions "in the past" is still waiting). This is generally all invisible to a single thread since the CPU still maintains the illusion of serial execution by the current thread by respecting dependencies, so from the point of view of the current thread of execution it is as-if the instructions were executed serially. So i think the memory barriers positions of my scalable MLock (that is a scalable lock) are ok, read about it here: https://sites.google.com/site/scalable68/scalable-mlock Thank you, Amine Moulay Ramdane.
Back to top | Article view | comp.programming.threads
csiph-web