eden-emu/eden - eden - InfoTonic - Git

Author	SHA1	Message	Date
Lioncash	ab6dfa4fa5	ring_buffer: Use std::atomic_size_t in a static assert Avoids the need to repeat "std::" twice	8 years ago
Lioncash	c51f8563a6	ring_buffer: Use std::hardware_destructive_interference_size to determine alignment size for avoiding false sharing MSVC 19.11 (A.K.A. VS 15.3)'s C++ standard library implements P0154R1 (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0154r1.html) which defines two new constants within the <new> header, std::hardware_destructive_interference_size and std::hardware_constructive_interference_size. std::hardware_destructive_interference_size defines the minimum recommended offset between two concurrently-accessed objects to avoid performance degradation due to contention introduced by the implementation (with the lower-bound being at least alignof(max_align_t)). In other words, the minimum offset between objects necessary to avoid false-sharing. std::hardware_constructive_interference_size on the other hand defines the maximum recommended size of contiguous memory occupied by two objects accessed wth temporal locality by concurrent threads (also defined to be at least alignof(max_align_t)). In other words the maximum size to promote true-sharing. So we can simply use this facility to determine the ideal alignment size. Unfortunately, only MSVC supports this right now, so we need to enclose it within an ifdef for the time being.	8 years ago
fearlessTobi	63c2e32e20	Port #4182 from Citra: "Prefix all size_t with std::"	8 years ago
MerryMage	112351d557	common: Implement a ring buffer	8 years ago