diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-08-20 10:54:56 +0200 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-09-02 17:59:31 +0200 |
commit | ba9dfcf92c8aeb832c6f2c7ea7c4150064960d63 (patch) | |
tree | 35f78d6069dfff6a44fd4def1cf1d0cf2d2cd4c4 /c-user/scheduling-concepts/introduction.rst | |
parent | c-user: Split up user extensions manager (diff) | |
download | rtems-docs-ba9dfcf92c8aeb832c6f2c7ea7c4150064960d63.tar.bz2 |
c-user: Split up scheduling concepts
Introduce a background section.
This makes it easier to automatically generate parts of the scheduling
concepts documentation in the future.
Update #3993.
Diffstat (limited to 'c-user/scheduling-concepts/introduction.rst')
-rw-r--r-- | c-user/scheduling-concepts/introduction.rst | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/c-user/scheduling-concepts/introduction.rst b/c-user/scheduling-concepts/introduction.rst new file mode 100644 index 0000000..92da6de --- /dev/null +++ b/c-user/scheduling-concepts/introduction.rst @@ -0,0 +1,42 @@ +.. SPDX-License-Identifier: CC-BY-SA-4.0 + +.. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR) + +Introduction +============ + +The concept of scheduling in real-time systems dictates the ability to provide +an immediate response to specific external events, particularly the necessity of +scheduling tasks to run within a specified time limit after the occurrence of +an event. For example, software embedded in life-support systems used to +monitor hospital patients must take instant action if a change in the patient's +status is detected. + +The component of RTEMS responsible for providing this capability is +appropriately called the scheduler. The scheduler's sole purpose is to +allocate the all important resource of processor time to the various tasks +competing for attention. + +The directives provided by the scheduler manager are: + +- :ref:`rtems_scheduler_ident` + +- :ref:`rtems_scheduler_ident_by_processor` + +- :ref:`rtems_scheduler_ident_by_processor_set` + +- :ref:`rtems_scheduler_get_maximum_priority` + +- :ref:`rtems_scheduler_map_priority_to_posix` + +- :ref:`rtems_scheduler_map_priority_from_posix` + +- :ref:`rtems_scheduler_get_processor` + +- :ref:`rtems_scheduler_get_processor_maximum` + +- :ref:`rtems_scheduler_get_processor_set` + +- :ref:`rtems_scheduler_add_processor` + +- :ref:`rtems_scheduler_remove_processor` |