Lines Matching full:threads
56 Locking. Data that is shared over threads is protected from concurrent
57 accesses via locking. E.g. the POSIX threads library, the Qt library
63 Message passing. No data is shared between threads, but threads exchange
85 threads is updated via transactions. After each transaction it is
99 threads primitives. DRD however does not support programs that use
108 <title>POSIX Threads Programming Model</title>
111 POSIX threads, also known as Pthreads, is the most widely available
116 The POSIX threads programming model is based on the following abstractions:
120 A shared address space. All threads running within the same
128 from or to write values to the memory shared by all threads
135 not mentioned in the POSIX threads standard, most
141 Threads. Each thread represents a concurrent activity.
148 defined in the POSIX threads standard: mutexes, condition variables,
166 For more information about POSIX threads, see also the Single UNIX
168 <ulink url="http://www.opengroup.org/onlinepubs/000095399/idx/threads.html">
184 Data races. One or more threads access the same memory location without
192 threads by holding a lock too long.
197 Improper use of the POSIX threads API. Most implementations of the POSIX
198 threads API have been optimized for runtime speed. Such implementations
205 Deadlock. A deadlock occurs when two or more threads wait for
211 False sharing. If threads that run on different processor cores
213 frequently, this will slow down the involved threads a lot due
225 improper use of the POSIX threads API.
249 memory operations performed by different threads. These ordering
263 performed by different threads, refer to the same memory location and at least
334 most programs do not share stack variables over threads.
359 allows to specify for how many joined threads memory access information
498 number of threads it becomes important to limit the amount of virtual
776 Threads must be able to make progress without being blocked for too long by
777 other threads. Sometimes a thread has to wait until a mutex or reader-writer
814 <title>Detected Errors: Misuse of the POSIX threads API</title>
818 threads API:
896 synchronization object to a POSIX threads function.
983 threads. It may be more convenient to suppress such races than to solve
1115 that <literal>count</literal> threads participate in each barrier and
1240 are built on top of POSIX threads, and hence are directly supported by
1242 <function>g_thread_init</function> before creating any threads, or
1245 url="http://library.gnome.org/devel/glib/stable/glib-Threads.html">GLib
1290 Threads?</ulink>, Recent changes to the Boost Thread library,
1308 work at a higher level compared to direct use of the POSIX threads API. While
1412 threads standard to call
1491 of the client program threads. This amount of data is limited to
1547 output from several threads getting mixed up. Either use
1554 lines of text produced by different threads get mixed
1582 <title>Using the POSIX Threads API Effectively</title>
1639 threads. Condition variables are often used to notify one or more
1640 threads about state changes of shared data. Unfortunately it is very
1643 let threads poll for changes of a state variable that is protected by
1742 Of the two POSIX threads implementations for Linux, only the
