Re:Yes, You Have Been Writing SPSC Queues Wrong
by gpderetta on Thursday December 15, 2016 @05:15PM
(#13189038)
The usual trick is for each side to cache the last value of the other side index so you only need to refresh the remote value when you "catch up".
Even without caching, padding is still a win as the shared to exclusive transition is less expensive than a request for ownership of an invalidated cache line (aka "single writer principle")
Even without caching, padding is still a win as the shared to exclusive transition is less expensive than a request for ownership of an invalidated cache line (aka "single writer principle")