Thread Local Storage Pointers
IntroductionThread local storage (or TLS) allows the application writer to store values inside a task’s control block, making the value specific to (local to) the task itself, and allowing each task to have its own unique value.
Thread local storage is most often used to store values that a single threaded program would otherwise store in a global variable. For example, many libraries include a global variable called errno. If a library function returns an error condition to the calling function, then the calling function can inspect the errno value to determine what the error was. In a single threaded application it is sufficient to declare errno as a global variable, but in a multi-threaded application each thread (task) must have its own unique errno value – otherwise one task might read an errno value that was intended for another task.
Thread Local Storage PointersFreeRTOS provides the application writer with a flexible thread local storage mechanism through the use of thread local storage pointers.
The configNUM_THREAD_LOCAL_STORAGE_POINTERS compile time configuration constant dimensions a per task array of void pointers (void*). The vTaskSetThreadLocalStoragePointer() API function is used to set a value within the array of void pointers, and pvTaskGetThreadLocalStoragePointer() API function is used to read a value from the array of void pointers.
Thread Local IntegersValues that have a size less than or equal to the size of a void pointer can be stored directly within the thread local storage pointer array. For example, if sizeof( void * ) is 4 then a 32-bit value can be stored in a void pointer variable, using a simple cast to avoid compiler warnings. However, if sizeof( void * ) is 2, then only a 16-bit value can be stored directly.
Thread Local StructuresThe previous example stored values directly into the thread local storage array. This next example demonstrates how to use a value in the array as a pointer to a structure that exists elsewhere in memory.