libstdc++-v3/doc/html/manual/ext_concurrency.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 30. Concurrency</title><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><meta name="keywords" content="
   2       ISO C++
   3     ,
   4       library
   5     "><meta name="keywords" content="
   6       ISO C++
   7     ,
   8       library
   9     "><meta name="keywords" content="
  10       ISO C++
  11     ,
  12       runtime
  13     ,
  14       library
  15     "><link rel="home" href="../index.html" title="The GNU C++ Library"><link rel="up" href="extensions.html" title="Part III.  Extensions"><link rel="prev" href="ext_demangling.html" title="Chapter 29. Demangling"><link rel="next" href="bk01pt03ch30s02.html" title="Implementation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 30. Concurrency</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ext_demangling.html">Prev</a> </td><th width="60%" align="center">Part III.
  16   Extensions
  17
  18 </th><td width="20%" align="right"> <a accesskey="n" href="bk01pt03ch30s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 30. Concurrency"><div class="titlepage"><div><div><h2 class="title"><a name="manual.ext.concurrency"></a>Chapter 30. Concurrency</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ext_concurrency.html#manual.ext.concurrency.design">Design</a></span></dt><dd><dl><dt><span class="section"><a href="ext_concurrency.html#manual.ext.concurrency.design.threads">Interface to Locks and Mutexes</a></span></dt><dt><span class="section"><a href="ext_concurrency.html#manual.ext.concurrency.design.atomics">Interface to Atomic Functions</a></span></dt></dl></dd><dt><span class="section"><a href="bk01pt03ch30s02.html">Implementation</a></span></dt><dd><dl><dt><span class="section"><a href="bk01pt03ch30s02.html#manual.ext.concurrency.impl.atomic_fallbacks">Using Builtin Atomic Functions</a></span></dt><dt><span class="section"><a href="bk01pt03ch30s02.html#manual.ext.concurrency.impl.thread">Thread Abstraction</a></span></dt></dl></dd><dt><span class="section"><a href="bk01pt03ch30s03.html">Use</a></span></dt></dl></div><div class="section" title="Design"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="manual.ext.concurrency.design"></a>Design</h2></div></div></div><div class="section" title="Interface to Locks and Mutexes"><div class="titlepage"><div><div><h3 class="title"><a name="manual.ext.concurrency.design.threads"></a>Interface to Locks and Mutexes</h3></div></div></div><p>The file <code class="filename">&lt;ext/concurrence.h&gt;</code>
  19 contains all the higher-level
  20 constructs for playing with threads. In contrast to the atomics layer,
  21 the concurrence layer consists largely of types. All types are defined within <code class="code">namespace __gnu_cxx</code>.
  22 </p><p>
  23 These types can be used in a portable manner, regardless of the
  24 specific environment. They are carefully designed to provide optimum
  25 efficiency and speed, abstracting out underlying thread calls and
  26 accesses when compiling for single-threaded situations (even on hosts
  27 that support multiple threads.)
  28 </p><p>The enumerated type <code class="code">_Lock_policy</code> details the set of
  29 available locking
  30 policies: <code class="code">_S_single</code>, <code class="code">_S_mutex</code>,
  31 and <code class="code">_S_atomic</code>.
  32 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="code">_S_single</code></p><p>Indicates single-threaded code that does not need locking.
  33 </p></li><li class="listitem"><p><code class="code">_S_mutex</code></p><p>Indicates multi-threaded code using thread-layer abstractions.
  34 </p></li><li class="listitem"><p><code class="code">_S_atomic</code></p><p>Indicates multi-threaded code using atomic operations.
  35 </p></li></ul></div><p>The compile-time constant <code class="code">__default_lock_policy</code> is set
  36 to one of the three values above, depending on characteristics of the
  37 host environment and the current compilation flags.
  38 </p><p>Two more datatypes make up the rest of the
  39 interface: <code class="code">__mutex</code>, and <code class="code">__scoped_lock</code>.
  40 </p><p>The scoped lock idiom is well-discussed within the C++
  41 community. This version takes a <code class="code">__mutex</code> reference, and
  42 locks it during construction of <code class="code">__scoped_lock</code> and
  43 unlocks it during destruction. This is an efficient way of locking
  44 critical sections, while retaining exception-safety.
  45 These types have been superseded in the ISO C++ 2011 standard by the
  46 mutex and lock types defined in the header
  47 <code class="filename">&lt;mutex&gt;</code>.
  48 </p></div><div class="section" title="Interface to Atomic Functions"><div class="titlepage"><div><div><h3 class="title"><a name="manual.ext.concurrency.design.atomics"></a>Interface to Atomic Functions</h3></div></div></div><p>
  49 Two functions and one type form the base of atomic support.
  50 </p><p>The type <code class="code">_Atomic_word</code> is a signed integral type
  51 supporting atomic operations.
  52 </p><p>
  53 The two functions functions are:
  54 </p><pre class="programlisting">
  55 _Atomic_word
  56 __exchange_and_add_dispatch(volatile _Atomic_word*, int);
  57
  58 void
  59 __atomic_add_dispatch(volatile _Atomic_word*, int);
  60 </pre><p>Both of these functions are declared in the header file
  61 &lt;ext/atomicity.h&gt;, and are in <code class="code">namespace __gnu_cxx</code>.
  62 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
  63 <code class="code">
  64 __exchange_and_add_dispatch
  65 </code>
  66 </p><p>Adds the second argument's value to the first argument. Returns the old value.
  67 </p></li><li class="listitem"><p>
  68 <code class="code">
  69 __atomic_add_dispatch
  70 </code>
  71 </p><p>Adds the second argument's value to the first argument. Has no return value.
  72 </p></li></ul></div><p>
  73 These functions forward to one of several specialized helper
  74 functions, depending on the circumstances. For instance,
  75 </p><p>
  76 <code class="code">
  77 __exchange_and_add_dispatch
  78 </code>
  79 </p><p>
  80 Calls through to either of:
  81 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="code">__exchange_and_add</code>
  82 </p><p>Multi-thread version. Inlined if compiler-generated builtin atomics
  83 can be used, otherwise resolved at link time to a non-builtin code
  84 sequence.
  85 </p></li><li class="listitem"><p><code class="code">__exchange_and_add_single</code>
  86 </p><p>Single threaded version. Inlined.</p></li></ul></div><p>However, only <code class="code">__exchange_and_add_dispatch</code>
  87 and <code class="code">__atomic_add_dispatch</code> should be used. These functions
  88 can be used in a portable manner, regardless of the specific
  89 environment. They are carefully designed to provide optimum efficiency
  90 and speed, abstracting out atomic accesses when they are not required
  91 (even on hosts that support compiler intrinsics for atomic
  92 operations.)
  93 </p><p>
  94 In addition, there are two macros
  95 </p><p>
  96 <code class="code">
  97 _GLIBCXX_READ_MEM_BARRIER
  98 </code>
  99 </p><p>
 100 <code class="code">
 101 _GLIBCXX_WRITE_MEM_BARRIER
 102 </code>
 103 </p><p>
 104 Which expand to the appropriate write and read barrier required by the
 105 host hardware and operating system.
 106 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ext_demangling.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="extensions.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bk01pt03ch30s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 29. Demangling </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> Implementation</td></tr></table></div></body></html>