VTK
9.1.0
|
Thread local storage for VTK objects. More...
#include <vtkSMPThreadLocal.h>
Public Types | |
typedef vtk::detail::smp::vtkSMPThreadLocalAPI< T >::iterator | iterator |
Subset of the standard iterator API. More... | |
Public Member Functions | |
vtkSMPThreadLocal () | |
Default constructor. More... | |
vtkSMPThreadLocal (const T &exemplar) | |
Constructor that allows the specification of an exemplar object which is used when constructing objects when Local() is first called. More... | |
T & | Local () |
This needs to be called mainly within a threaded execution path. More... | |
size_t | size () |
Return the number of thread local objects that have been initialized. More... | |
iterator | begin () |
Returns a new iterator pointing to the beginning of the local storage container. More... | |
iterator | end () |
Returns a new iterator pointing to past the end of the local storage container. More... | |
Thread local storage for VTK objects.
A thread local object is one that maintains a copy of an object of the template type for each thread that processes data. vtkSMPThreadLocal creates storage for all threads but the actual objects are created the first time Local() is called. Note that some of the vtkSMPThreadLocal API is not thread safe. It can be safely used in a multi-threaded environment because Local() returns storage specific to a particular thread, which by default will be accessed sequentially. It is also thread-safe to iterate over vtkSMPThreadLocal as long as each thread creates its own iterator and does not change any of the thread local objects.
A common design pattern in using a thread local storage object is to write/accumulate data to local object when executing in parallel and then having a sequential code block that iterates over the whole storage using the iterators to do the final accumulation.
Definition at line 87 of file vtkSMPThreadLocal.h.
typedef vtk::detail::smp::vtkSMPThreadLocalAPI<T>::iterator vtkSMPThreadLocal< T >::iterator |
Subset of the standard iterator API.
The most common design pattern is to use iterators in a sequential code block and to use only the thread local objects in parallel code blocks. It is thread safe to iterate over the thread local containers as long as each thread uses its own iterator and does not modify objects in the container.
Definition at line 132 of file vtkSMPThreadLocal.h.
|
inline |
|
inlineexplicit |
Constructor that allows the specification of an exemplar object which is used when constructing objects when Local() is first called.
Note that a copy of the exemplar is created using its copy constructor.
Definition at line 103 of file vtkSMPThreadLocal.h.
|
inline |
This needs to be called mainly within a threaded execution path.
It will create a new object (local to the thread so each thread get their own when calling Local) which is a copy of exemplar as passed to the constructor (or a default object if no exemplar was provided) the first time it is called. After the first time, it will return the same object.
Definition at line 116 of file vtkSMPThreadLocal.h.
|
inline |
Return the number of thread local objects that have been initialized.
Definition at line 121 of file vtkSMPThreadLocal.h.
|
inline |
Returns a new iterator pointing to the beginning of the local storage container.
Thread safe.
Definition at line 138 of file vtkSMPThreadLocal.h.
|
inline |
Returns a new iterator pointing to past the end of the local storage container.
Thread safe.
Definition at line 144 of file vtkSMPThreadLocal.h.