<div dir="ltr">Looks good.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 12, 2021 at 8:07 AM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">---<br>
c-user/glossary.rst | 41 ++++++++++++++++++++++++++++++++++++++---<br>
1 file changed, 38 insertions(+), 3 deletions(-)<br>
<br>
diff --git a/c-user/glossary.rst b/c-user/glossary.rst<br>
index b3527a7..5a06c10 100644<br>
--- a/c-user/glossary.rst<br>
+++ b/c-user/glossary.rst<br>
@@ -194,6 +194,14 @@ Glossary<br>
This term is an acronym for Cathode Ray Tube. Normally used in reference to<br>
the man-machine interface.<br>
<br>
+ current priority<br>
+ The current priority of a :term:`task` is the :term:`task priority` with<br>
+ respect to the :term:`home scheduler` of the task. It is an aggregation of<br>
+ the :term:`real priority` and temporary priority adjustments due to locking<br>
+ protocols, the rate-monotonic period objects on some schedulers such as EDF,<br>
+ and the :term:`POSIX` sporadic server. The current priority is an<br>
+ :term:`eligible priority`.<br>
+<br>
deadline<br>
A fixed time limit by which a task must have completed a set of actions.<br>
Beyond this point, the results are of reduced value and may even be<br>
@@ -246,6 +254,12 @@ Glossary<br>
This term is an acronym for<br>
`Executable and Linkable Format <<a href="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Executable_and_Linkable_Format</a>>`_.<br>
<br>
+ eligible priority<br>
+ An eligible priority of a :term:`task` is the :term:`task priority` with<br>
+ respect to the corresponding :term:`eligible scheduler` of the task. An<br>
+ eligible priority is either the :term:`current priority` and a<br>
+ :term:`helping priority` of a task.<br>
+<br>
eligible scheduler<br>
An eligible scheduler of a :term:`task` is a :term:`scheduler` which can be<br>
used by the task to allocate a processor for the task.<br>
@@ -366,6 +380,11 @@ Glossary<br>
dispatch is marked as necessary, then the next thread dispatch will make<br>
the heir task the executing task.<br>
<br>
+ helping priority<br>
+ A helping priority of a :term:`task` is the :term:`task priority` with<br>
+ respect to the corresponding :term:`helping scheduler` of the task. A<br>
+ helping priority is an :term:`eligible priority`.<br>
+<br>
helping scheduler<br>
A helping scheduler of a :term:`task` is a :term:`scheduler` which is a<br>
:term:`eligible scheduler` and which is not the :term:`home scheduler` of<br>
@@ -632,9 +651,9 @@ Glossary<br>
another task.<br>
<br>
priority<br>
- A mechanism used to represent the relative importance of an element in a<br>
- set of items. RTEMS uses priority to determine which task should<br>
- execute.<br>
+ The priority is a mechanism used to represent the relative importance of an<br>
+ element in a set of items. RTEMS uses :term:`task priorities <task priority>` to determine<br>
+ which :term:`task` should execute.<br>
<br>
priority boosting<br>
A simple approach to extend the priority inheritance protocol for<br>
@@ -686,6 +705,14 @@ Glossary<br>
decided that other tasks are currently more important. A task that is<br>
ready to execute and has a processor assigned is called scheduled.<br>
<br>
+ real priority<br>
+ Each :term:`task` has exactly one real priority. The real priority is<br>
+ always with respect to the :term:`home scheduler` of a task. It is defined<br>
+ during task initialization. It may be changed by directives such as<br>
+ :c:func:`rtems_task_set_priority` and<br>
+ :c:func:`rtems_task_set_scheduler`. The real priority is the foundation<br>
+ of the :term:`current priority`.<br>
+<br>
real-time<br>
A term used to describe systems which are characterized by requiring<br>
deterministic response times to external stimuli. The external stimuli<br>
@@ -959,6 +986,14 @@ Glossary<br>
Task migration happens in case a task stops execution on one processor<br>
and resumes execution on another processor.<br>
<br>
+ task priority<br>
+ A task priority of a :term:`task` determines its importance with respect to<br>
+ other tasks. The scheduler use task priorities to determine which<br>
+ :term:`ready task` gets a processor allocated. The<br>
+ :term:`eligible priorities <eligible priority>` of a task define the position of the task in a<br>
+ :term:`wait queue` which uses the priority discipline. Each task has at<br>
+ least the :term:`real priority`.<br>
+<br>
task processor affinity<br>
The set of processors on which a task is allowed to execute.<br>
<br>
-- <br>
2.26.2<br>
<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>