blob: a203bef3cf268728a4f990b0594f20df3ea2d014 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
SPDX-License-Identifier: CC-BY-SA-4.0
copyrights:
- Copyright (C) 2021 embedded brains GmbH & Co. KG
enabled-by: true
glossary-type: term
links:
- role: glossary-member
uid: group
term: scheduler operation
text: |
When the ${../glossary/ownertask:/term} executes a ${../glossary/job:/term} of
a rate monotonic period, it often competes with other
${/glossary/task:/plural} for CPU time. What exactly happens depends on the
${/glossary/scheduler-home:/term} of the ${/glossary/task:/term}. Directives
like ${../if/period:/name} or ${../if/cancel:/name} invoke
${/glossary/scheduler:/term} operations like ``release_job`` or ``cancel_job``.
The ${/glossary/scheduler-home:/term} often changes the
${/glossary/priority-task:/term}.
type: glossary
|
