rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-07-05 14:04:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

c-user: Fix reference

Browse Source
This commit is contained in:
Sebastian Huber 2018-04-30 15:03:05 +02:00
parent 06519a5b96
commit 1dbbc76f11
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
c-user/symmetric_multiprocessing_services.rst
View File

@ -208,12 +208,12 @@ Clustered scheduling was implemented for RTEMS SMP to best use the cache
topology of a system and to keep the worst-case latencies under control. The topology of a system and to keep the worst-case latencies under control. The
low-level SMP locks use FIFO ordering. So, the worst-case run-time of low-level SMP locks use FIFO ordering. So, the worst-case run-time of
operations increases with each processor involved. The scheduler configuration operations increases with each processor involved. The scheduler configuration
is quite flexible and done at link-time, see :ref:`Configuring Clustered is quite flexible and done at link-time, see
Schedulers`. It is possible to re-assign processors to schedulers during :ref:`ConfigurationSchedulersClustered`. It is possible to re-assign
run-time via :ref:`rtems_scheduler_add_processor() processors to schedulers during run-time via
<rtems_scheduler_add_processor>` and :ref:`rtems_scheduler_remove_processor() :ref:`rtems_scheduler_add_processor() <rtems_scheduler_add_processor>` and
<rtems_scheduler_remove_processor>`. The schedulers are implemented in an :ref:`rtems_scheduler_remove_processor() <rtems_scheduler_remove_processor>`.
object-oriented fashion. The schedulers are implemented in an object-oriented fashion.
The problem is to provide synchronization The problem is to provide synchronization
primitives for inter-cluster synchronization (more than one cluster is involved primitives for inter-cluster synchronization (more than one cluster is involved