rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-17 09:31:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

c-user: Mention thread pinning

Browse Source 
Close #3508.
This commit is contained in:
Sebastian Huber 2018-09-07 15:47:43 +02:00
parent d90c8137a8
commit 7c58036961
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
c-user/symmetric_multiprocessing_services.rst
View File

@ -809,3 +809,25 @@ RTEMS provides two means for per-processor data:
`<rtems/score/percpudata.h> <https://git.rtems.org/rtems/tree/cpukit/include/rtems/score/percpudata.h>`_.
This API is not intended for general application use. Please ask on the
development mailing list in case you want to use it.
Thread Pinning
--------------
Thread pinning ensures that a thread is only dispatched to the processor on
which it is pinned. It may be used to access per-processor data structures in
critical sections with enabled thread dispatching, e.g. a pinned thread is
allowed to block. The `_Thread_Pin()` operation will pin the executing thread
to its current processor. A thread may be pinned recursively, the last unpin
request via `_Thread_Unpin()` revokes the pinning.
Thread pinning should be used only for short critical sections and not all
the time. Thread pinning is a very low overhead operation in case the
thread is not preempted during the pinning. A preemption will result in
scheduler operations to ensure that the thread executes only on its pinned
processor. Thread pinning must be used with care, since it prevents help
through the locking protocols. This makes the :ref:`OMIP <OMIP>` and
:ref:`MrsP <MrsP>` locking protocols ineffective if pinned threads are
involved.
The thread pinning is not intended for general application use. Please ask on
the development mailing list in case you want to use it.