Reference documentation for deal.II version Git cb0bd54b52 2019-09-21 16:31:22 -0400
\(\newcommand{\dealcoloneq}{\mathrel{\vcenter{:}}=}\)
Public Member Functions | Private Attributes | List of all members
Threads::ThreadLocalStorage< T > Class Template Reference

A class that provides a separate storage location on each thread that accesses the object. More...

#include <deal.II/base/thread_local_storage.h>

Inheritance diagram for Threads::ThreadLocalStorage< T >:
[legend]

Public Member Functions

 ThreadLocalStorage ()=default
 
 ThreadLocalStorage (const T &t)
 
 ThreadLocalStorage (const ThreadLocalStorage< T > &t)
 
T & get ()
 
T & get (bool &exists)
 
 operator T& ()
 
ThreadLocalStorage< T > & operator= (const T &t)
 
void clear ()
 
tbb::enumerable_thread_specific< T > & get_implementation ()
 

Private Attributes

tbb::enumerable_thread_specific< T > data
 

Detailed Description

template<typename T>
class Threads::ThreadLocalStorage< T >

A class that provides a separate storage location on each thread that accesses the object.

This class offers ways so that every thread that accesses it has its own copy of an object of type T. In essence, accessing this object can never result in race conditions in multithreaded programs since no other thread than the current one can ever access it.

The class builds on the Threading Building Blocks's tbb::enumerable_thread_specific class but wraps it in such a way that this class can also be used when deal.II is configured not to use threads at all – in that case, this class simply stores a single copy of an object of type T.

Construction and destruction

Objects of this class can either be default constructed or by providing an "exemplar", i.e. an object of type T so that every time we need to create a T on a thread that doesn't already have such an object, it is copied from the exemplar.

Upon destruction of objects of this class, all T objects that correspond to threads that have accessed this object are destroyed. Note that this may be before the time when a thread is terminated.

Access

The T object stored by this object can be accessed using the get() function. It provides a reference to a unique object when accessed from different threads. Objects of type T are created lazily, i.e. they are only created whenever a thread actually calls get().

Definition at line 72 of file thread_local_storage.h.

Constructor & Destructor Documentation

◆ ThreadLocalStorage() [1/3]

template<typename T>
Threads::ThreadLocalStorage< T >::ThreadLocalStorage ( )
default

Default constructor. Initialize each thread local object using its default constructor.

◆ ThreadLocalStorage() [2/3]

template<typename T>
Threads::ThreadLocalStorage< T >::ThreadLocalStorage ( const T &  t)
inlineexplicit

A kind of copy constructor. Initialize each thread local object by copying the given object.

Definition at line 189 of file thread_local_storage.h.

◆ ThreadLocalStorage() [3/3]

template<typename T>
Threads::ThreadLocalStorage< T >::ThreadLocalStorage ( const ThreadLocalStorage< T > &  t)
inline

Copy constructor. Initialize each thread local object with the corresponding object of the given object.

Definition at line 195 of file thread_local_storage.h.

Member Function Documentation

◆ get() [1/2]

template<typename T >
T & Threads::ThreadLocalStorage< T >::get ( )
inline

Return a reference to the data stored by this object for the current thread this function is called on.

Note that there is no member function get() that is const and returns a const reference as one would expect. The reason is that if such a member function were called on a thread for which no thread-local object has been created yet, then one has to create such an object first which would certainly be a non-constant operation. If you need to call the get() function for a member variable of a class from a const member function, then you need to declare the member variable mutable to allow such access.

Definition at line 203 of file thread_local_storage.h.

◆ get() [2/2]

template<typename T >
T & Threads::ThreadLocalStorage< T >::get ( bool &  exists)
inline

Same as above, except that exists is set to true if an element was already present for the current thread; false otherwise.

Definition at line 215 of file thread_local_storage.h.

◆ operator T&()

template<typename T>
Threads::ThreadLocalStorage< T >::operator T & ( )

Conversion operator that simply converts the thread-local object to the data type that it stores. This function is equivalent to calling the get() member function; it's purpose is to make the TLS object look more like the object it is storing.

◆ operator=()

template<typename T>
ThreadLocalStorage< T > & Threads::ThreadLocalStorage< T >::operator= ( const T &  t)
inline

Copy the given argument into the storage space used to represent the current thread. Calling this function as tls_data = object is equivalent to calling tls_data.get() = object. The intent of this operator is to make the ThreadLocalStorage object look more like the object it represents on the current thread.

Parameters
tThe object to be copied into the storage space used for the current thread.
Returns
The current object, after the changes have been made

Definition at line 235 of file thread_local_storage.h.

◆ clear()

template<typename T >
void Threads::ThreadLocalStorage< T >::clear ( )
inline

Remove the thread-local objects stored for all threads that have created one with this object (i.e., that have called get() at least once on this thread. This includes the current thread. If you call get() subsequently on this or any other thread, new objects will again be created.

If deal.II has been configured to not use multithreading, then this function does not do anything at all. Note that this of course has different semantics as in the multithreading context the objects are deleted and created again (possible by copying from a sample object, if the appropriate constructor of this class was called), whereas in the multithreaded context the object is simply not touched at all. At the same time, the purpose of this function is to release memory other threads may have allocated for their own thread local objects after which every use of this object will require some kind of initialization. This is necessary both in the multithreaded or non- multithreaded case.

Definition at line 258 of file thread_local_storage.h.

◆ get_implementation()

template<typename T >
tbb::enumerable_thread_specific< T > & Threads::ThreadLocalStorage< T >::get_implementation ( )
inline

Return a reference to the internal Threading Building Blocks implementation. This function is really only useful if deal.II has been configured with multithreading and has no useful purpose otherwise.

Definition at line 249 of file thread_local_storage.h.

Member Data Documentation

◆ data

template<typename T>
tbb::enumerable_thread_specific<T> Threads::ThreadLocalStorage< T >::data
private

The data element we store. If we support threads, then this object will be of a type that provides a separate object for each thread. Otherwise, it is simply a single object of type T.

Definition at line 180 of file thread_local_storage.h.


The documentation for this class was generated from the following file: