mirror of
https://git.rtems.org/rtems-docs/
synced 2025-05-17 05:31:47 +08:00
c-user: Add TAS and TTAS terms
This commit is contained in:
parent
87b4d03b35
commit
90a3c414ce
@ -668,6 +668,9 @@ Glossary
|
||||
target
|
||||
The system on which the application will ultimately execute.
|
||||
|
||||
TAS
|
||||
An acronym for Test-And-Set.
|
||||
|
||||
task
|
||||
thread
|
||||
A logically complete thread of execution. It consists normally of a set
|
||||
@ -741,6 +744,9 @@ Glossary
|
||||
missed. Rate Monotonic Scheduling can be used to determine if all
|
||||
deadlines will be met under transient overload.
|
||||
|
||||
TTAS
|
||||
An acronym for Test and Test-And-Set.
|
||||
|
||||
user extensions
|
||||
Software routines provided by the application to enhance the
|
||||
functionality of RTEMS.
|
||||
|
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user