Changeset 464d541 in rtems-docs


Ignore:
Timestamp:
Mar 7, 2018, 1:18:10 PM (14 months ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
c65aeed
Parents:
690b7f9
git-author:
Sebastian Huber <sebastian.huber@…> (03/07/18 13:18:10)
git-committer:
Sebastian Huber <sebastian.huber@…> (03/07/18 14:33:02)
Message:

c-user: Use uniprocessor throughout

Location:
c-user
Files:
7 edited

Legend:

Unmodified
Added
Removed
  • c-user/configuring_a_system.rst

    r690b7f9 r464d541  
    604604NOTES:
    605605    This configuration option is only used in SMP configurations.  In
    606     uni-processor configurations, the :ref:`PriorityCeiling` is used for MrsP
     606    uniprocessor configurations, the :ref:`PriorityCeiling` is used for MrsP
    607607    semaphores and thus no extra memory is necessary.
    608608
     
    14361436NOTES:
    14371437    If there are more processors available than configured, the rest will be
    1438     ignored.  This configuration define is ignored in uni-processor
     1438    ignored.  This configuration define is ignored in uniprocessor
    14391439    configurations.
    14401440
     
    33283328DESCRIPTION:
    33293329    The Constant Bandwidth Server Scheduler (CBS) is an alternative scheduler
    3330     in RTEMS for uni-processor applications. The CBS is a budget aware
     3330    in RTEMS for uniprocessor applications. The CBS is a budget aware
    33313331    extension of EDF scheduler. The goal of this scheduler is to ensure
    33323332    temporal isolation of tasks. The CBS is equipped with a set of additional
     
    33603360DESCRIPTION:
    33613361    The Earliest Deadline First Scheduler (EDF) is an alternative scheduler in
    3362     RTEMS for uni-processor applications. The EDF schedules tasks with dynamic
     3362    RTEMS for uniprocessor applications. The EDF schedules tasks with dynamic
    33633363    priorities equal to deadlines. The deadlines are declared using only Rate
    33643364    Monotonic manager which handles periodic behavior.  Period is always equal
     
    34583458DESCRIPTION:
    34593459    The Deterministic Priority Scheduler is the default scheduler in RTEMS for
    3460     uni-processor applications and is designed for predictable performance
     3460    uniprocessor applications and is designed for predictable performance
    34613461    under the highest loads.  It can block or unblock a thread in a constant
    34623462    amount of time.  This scheduler requires a variable amount of memory based
  • c-user/interrupt_manager.rst

    r690b7f9 r464d541  
    342342    This directive will not cause the calling task to be preempted.
    343343
    344     This directive is only available in uni-processor configurations.  The
     344    This directive is only available in uniprocessor configurations.  The
    345345    directive ``rtems_interrupt_local_disable`` is available in all
    346346    configurations.
     
    415415    This directive will not cause the calling task to be preempted.
    416416
    417     This directive is only available in uni-processor configurations.  The
     417    This directive is only available in uniprocessor configurations.  The
    418418    directive ``rtems_interrupt_local_enable`` is available in all
    419419    configurations.
     
    455455    This directive will not cause the calling task to be preempted.
    456456
    457     This directive is only available in uni-processor configurations.  The
     457    This directive is only available in uniprocessor configurations.  The
    458458    directives ``rtems_interrupt_local_disable`` and
    459459    ``rtems_interrupt_local_enable`` are available in all configurations.
  • c-user/key_concepts.rst

    r690b7f9 r464d541  
    360360non-preemptive sections present with priority boosting
    361361:cite:`Brandenburg:2013:OMIP`.  The :math:`m` denotes the number of processors
    362 in the system.  Similar to the uni-processor priority inheritance protocol, the
     362in the system.  Similar to the uniprocessor priority inheritance protocol, the
    363363OMIP mutexes do not need any external configuration data, e.g. a ceiling
    364364priority.  This makes them a good choice for general purpose libraries that
     
    379379in FIFO or priority order.
    380380
    381 In uni-processor configurations, the priority queuing discipline just orders
     381In uniprocessor configurations, the priority queuing discipline just orders
    382382the threads according to their current priority and in FIFO order in case of
    383383equal priorities.  However, in SMP configurations, the situation is a bit more
  • c-user/self_contained_objects.rst

    r690b7f9 r464d541  
    123123The :c:type:`rtems_mutex` and :c:type:`rtems_recursive_mutex` objects provide
    124124mutual-exclusion synchronization using the :ref:`PriorityInheritance` in
    125 uni-processor configurations or the :ref:`OMIP` in SMP configurations.
     125uniprocessor configurations or the :ref:`OMIP` in SMP configurations.
    126126Recursive locking should be used with care :cite:`Williams:2012:CA`.  The
    127127storage space for these object must be provided by the user.  There are no
  • c-user/semaphore_manager.rst

    r690b7f9 r464d541  
    115115
    116116RTEMS supports the :ref:`MrsP` for local, binary semaphores that use the
    117 priority task wait queue blocking discipline.  In uni-processor configurations,
     117priority task wait queue blocking discipline.  In uniprocessor configurations,
    118118the :ref:`PriorityCeiling` is used instead.
    119119
  • c-user/symmetric_multiprocessing_services.rst

    r690b7f9 r464d541  
    305305==================
    306306
    307 Most operating system services provided by the uni-processor RTEMS are
     307Most operating system services provided by the uniprocessor RTEMS are
    308308available in SMP configurations as well.  However, applications designed for an
    309 uni-processor environment may need some changes to correctly run in an SMP
     309uniprocessor environment may need some changes to correctly run in an SMP
    310310configuration.
    311311
    312312As discussed earlier, SMP systems have opportunities for true parallelism which
    313 was not possible on uni-processor systems. Consequently, multiple techniques
    314 that provided adequate critical sections on uni-processor systems are unsafe on
     313was not possible on uniprocessor systems. Consequently, multiple techniques
     314that provided adequate critical sections on uniprocessor systems are unsafe on
    315315SMP systems. In this section, some of these unsafe techniques will be
    316316discussed.
     
    334334-----------------------------------------
    335335
    336 On a uni-processor system, it is safe to assume that when the highest priority
     336On a uniprocessor system, it is safe to assume that when the highest priority
    337337task in an application executes, it will execute without being preempted until
    338338it voluntarily blocks. Interrupts may occur while it is executing, but there
     
    348348executing. It should be assumed that every processor is executing another
    349349application task. Further, those tasks will be ones which would not have been
    350 executed in a uni-processor configuration and should be assumed to have data
     350executed in a uniprocessor configuration and should be assumed to have data
    351351synchronization conflicts with what was formerly the highest priority task
    352352which executed without conflict.
     
    356356
    357357A thread which disables preemption prevents that a higher priority thread gets
    358 hold of its processor involuntarily.  In uni-processor configurations, this can
     358hold of its processor involuntarily.  In uniprocessor configurations, this can
    359359be used to ensure mutual exclusion at thread level.  In SMP configurations,
    360360however, more than one executing thread may exist.  Thus, it is impossible to
     
    367367-----------------------
    368368
    369 A low overhead means that ensures mutual exclusion in uni-processor
     369A low overhead means that ensures mutual exclusion in uniprocessor
    370370configurations is the disabling of interrupts around a critical section.  This
    371371is commonly used in device driver code.  In SMP configurations, however,
     
    393393interrupt locks.  The interrupt locks are a simple API layer on top of the SMP
    394394locks used for low-level synchronization in the operating system core.
    395 Currently, they are implemented as a ticket lock.  In uni-processor
     395Currently, they are implemented as a ticket lock.  In uniprocessor
    396396configurations, they degenerate to simple interrupt disable/enable sequences by
    397397means of the C pre-processor.  It is disallowed to acquire a single interrupt
     
    471471
    472472Timer service routines run in the context of the clock interrupt.  On
    473 uni-processor configurations, it is sufficient to disable interrupts and remove
     473uniprocessor configurations, it is sufficient to disable interrupts and remove
    474474a timer from the set of active timers to stop it.  In SMP configurations,
    475475however, the timer service routine may already run and wait on an SMP lock
     
    521521
    522522DESCRIPTION:
    523     In uni-processor configurations, a value of one will be returned.
     523    In uniprocessor configurations, a value of one will be returned.
    524524
    525525    In SMP configurations, this returns the value of a global variable set
     
    550550
    551551DESCRIPTION:
    552     In uni-processor configurations, a value of zero will be returned.
     552    In uniprocessor configurations, a value of zero will be returned.
    553553
    554554    In SMP configurations, an architecture specific method is used to obtain the
  • c-user/timer_manager.rst

    r690b7f9 r464d541  
    6868associated with all task-based timers.  This task executes at a priority
    6969specified by :ref:`rtems_timer_initiate_server() <rtems_timer_initiate_server>`
    70 and it may have a priority of zero (the highest priority).  In uni-processor
     70and it may have a priority of zero (the highest priority).  In uniprocessor
    7171configurations, it is created non-preemptible.
    7272
Note: See TracChangeset for help on using the changeset viewer.