Home
last modified time | relevance | path

Searched refs:barrier (Results 1 – 2 of 2) sorted by relevance

/rocksdb-6.9/third-party/folly/folly/synchronization/test/
DDistributedMutexTest.cpp42 auto&& barrier = std::atomic<int>{0}; in basicNThreads()
77 auto&& barrier = std::atomic<int>{0}; in lockWithTryAndTimedNThreads()
84 EXPECT_EQ(barrier.fetch_add(1, std::memory_order_relaxed), 0); in lockWithTryAndTimedNThreads()
86 EXPECT_EQ(barrier.fetch_sub(1, std::memory_order_relaxed), 1); in lockWithTryAndTimedNThreads()
135 auto&& barrier = std::atomic<int>{0}; in combineNThreads()
179 auto&& barrier = std::atomic<int>{0}; in combineWithLockNThreads()
234 auto&& barrier = std::atomic<int>{0}; in combineWithTryLockNThreads()
306 auto&& barrier = std::atomic<int>{0}; in combineWithLockTryAndTimedNThreads()
899 auto& barrier = barriers[j % kNumMutexes]; in concurrentLocksManyMutexes() local
995 auto&& barrier = std::atomic<std::uint64_t>{0}; in concurrentExceptionPropagationStress()
[all …]
/rocksdb-6.9/docs/_posts/
D2018-11-21-delete-range.markdown191 `DeleteRange`’s negative impact on read perf is a barrier to its adoption. The