diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2017-02-03 11:55:29 +0100 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2017-02-03 11:55:29 +0100 |
commit | 90a3c414ce86abcdef261579be6570a8b559498e (patch) | |
tree | 7d007af4926265379591ad23b68ffa89b8c6e576 /c-user/symmetric_multiprocessing_services.rst | |
parent | c-user: Update scheduler helping protocol (diff) | |
download | rtems-docs-90a3c414ce86abcdef261579be6570a8b559498e.tar.bz2 |
c-user: Add TAS and TTAS terms
Diffstat (limited to 'c-user/symmetric_multiprocessing_services.rst')
-rw-r--r-- | c-user/symmetric_multiprocessing_services.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/c-user/symmetric_multiprocessing_services.rst b/c-user/symmetric_multiprocessing_services.rst index 51d4eff..01246ae 100644 --- a/c-user/symmetric_multiprocessing_services.rst +++ b/c-user/symmetric_multiprocessing_services.rst @@ -643,8 +643,8 @@ variables, Updates of the heir thread are done via a normal store operation. The thread dispatch necessary indicator of another processor is set as a side-effect of an inter-processor interrupt. So, this change notification works without the use -of locks. The thread context is protected by a TTAS lock embedded in the -context to ensure that it is used on at most one processor at a time. +of locks. The thread context is protected by a :term:`TTAS` lock embedded in +the context to ensure that it is used on at most one processor at a time. Normally, only thread-specific or per-processor locks are used during a thread dispatch. This implementation turned out to be quite efficient and no lock contention was observed in the testsuite. The heavy-weight thread dispatch |