TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The C11 and C++11 Concurrency Model (2014) [pdf]

63 点作者 clemlais超过 9 年前

2 条评论

mrpopo超过 9 年前
The absolute minimum that average users of the C++ memory ordering system in std atomic loads, etc. [1] should know is that the default memory access scheme is &#x27;sequentially consistent ordering&#x27;, whereas to get the ultimate performance, one should use the &#x27;relaxed&#x27; scheme, or alternatively use &#x27;release&#x2F;acquire&#x27; as described both in the article and in [1].<p>[1] <a href="http:&#x2F;&#x2F;en.cppreference.com&#x2F;w&#x2F;cpp&#x2F;atomic&#x2F;memory_order" rel="nofollow">http:&#x2F;&#x2F;en.cppreference.com&#x2F;w&#x2F;cpp&#x2F;atomic&#x2F;memory_order</a>
评论 #10643053 未加载
评论 #10642951 未加载
评论 #10643078 未加载
chubot超过 9 年前
What are some applications that use &quot;relaxed memory concurrency&quot;? Which ones really benefit from the performance increase?<p>How does it compare with using lock-free &#x2F; immutable data structures? IMO this strategy is less error prone and easier to test. I&#x27;ve written multi-threaded C++, but mostly before C++11.
评论 #10643280 未加载
评论 #10643333 未加载