c-user: Fix format

Update #3836.
This commit is contained in:
Sebastian Huber 2020-03-17 15:04:37 +01:00
parent 5e54ffe819
commit f75e0bee48
2 changed files with 36 additions and 36 deletions

View File

@ -201,37 +201,37 @@ DEFAULT VALUE:
to 255. to 255.
DESCRIPTION: DESCRIPTION:
For the schedulers For the schedulers
* :ref:`SchedulerPriority`, which is the default in uniprocessor * :ref:`SchedulerPriority`, which is the default in uniprocessor
configurations and can be configured through the configurations and can be configured through the
:ref:`CONFIGURE_SCHEDULER_PRIORITY` configuration option, :ref:`CONFIGURE_SCHEDULER_PRIORITY` configuration option,
* :ref:`SchedulerSMPPriority` which can be configured through the * :ref:`SchedulerSMPPriority` which can be configured through the
:ref:`CONFIGURE_SCHEDULER_PRIORITY_SMP` configuration option, and :ref:`CONFIGURE_SCHEDULER_PRIORITY_SMP` configuration option, and
* :ref:`SchedulerSMPPriorityAffinity` which can be configured through the * :ref:`SchedulerSMPPriorityAffinity` which can be configured through the
:ref:`CONFIGURE_SCHEDULER_PRIORITY_AFFINITY_SMP` configuration option :ref:`CONFIGURE_SCHEDULER_PRIORITY_AFFINITY_SMP` configuration option
this configuration option specifies the maximum numeric priority of any task this configuration option specifies the maximum numeric priority of any task
for these schedulers and one less that the number of priority levels for for these schedulers and one less that the number of priority levels for
these schedulers. For all other schedulers provided by RTEMS, this these schedulers. For all other schedulers provided by RTEMS, this
configuration option has no effect. configuration option has no effect.
NOTES: NOTES:
The numerically greatest priority is the logically lowest priority in the The numerically greatest priority is the logically lowest priority in the
system and will thus be used by the IDLE task. system and will thus be used by the IDLE task.
Priority zero (0) is reserved for internal use by RTEMS and is not available Priority zero (0) is reserved for internal use by RTEMS and is not available
to applications. to applications.
Reducing the number of priorities through this configuration option reduces Reducing the number of priorities through this configuration option reduces
the amount of memory allocated by the schedulers listed above. These the amount of memory allocated by the schedulers listed above. These
schedulers use a chain control structure per priority and this structure schedulers use a chain control structure per priority and this structure
consists of three pointers. On a 32-bit architecture, the allocated memory consists of three pointers. On a 32-bit architecture, the allocated memory
is 12 bytes * (``CONFIGURE_MAXIMUM_PRIORITY`` + 1), e.g. 3072 bytes for 256 is 12 bytes * (``CONFIGURE_MAXIMUM_PRIORITY`` + 1), e.g. 3072 bytes for 256
priority levels (default), 48 bytes for 4 priority levels priority levels (default), 48 bytes for 4 priority levels
(``CONFIGURE_MAXIMUM_PRIORITY == 3``). (``CONFIGURE_MAXIMUM_PRIORITY == 3``).
.. index:: CONFIGURE_MAXIMUM_PROCESSORS .. index:: CONFIGURE_MAXIMUM_PROCESSORS
@ -288,12 +288,12 @@ DEFAULT VALUE:
`PTHREAD_SETNAME_NP(3) <http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html>`_. `PTHREAD_SETNAME_NP(3) <http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html>`_.
DESCRIPTION: DESCRIPTION:
This configuration parameter specifies the maximum thread name size This configuration parameter specifies the maximum thread name size
including the terminating `NUL` character. including the terminating `NUL` character.
NOTES: NOTES:
The size of the thread control block is increased by the maximum thread name The size of the thread control block is increased by the maximum thread name
size. This configuration option is available since RTEMS 5.1. size. This configuration option is available since RTEMS 5.1.
.. index:: CONFIGURE_MEMORY_OVERHEAD .. index:: CONFIGURE_MEMORY_OVERHEAD

View File

@ -38,11 +38,11 @@ DESCRIPTION:
NOTES: NOTES:
A correctly configured system must configure the following to be consistent: A correctly configured system must configure the following to be consistent:
- ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT`` - ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT``
- ``CONFIGURE_TASK_STACK_ALLOCATOR`` - ``CONFIGURE_TASK_STACK_ALLOCATOR``
- ``CONFIGURE_TASK_STACK_DEALLOCATOR`` - ``CONFIGURE_TASK_STACK_DEALLOCATOR``
.. index:: CONFIGURE_TASK_STACK_ALLOCATOR_INIT .. index:: CONFIGURE_TASK_STACK_ALLOCATOR_INIT
@ -72,11 +72,11 @@ DESCRIPTION:
NOTES: NOTES:
A correctly configured system must configure the following to be consistent: A correctly configured system must configure the following to be consistent:
- ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT`` - ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT``
- ``CONFIGURE_TASK_STACK_ALLOCATOR`` - ``CONFIGURE_TASK_STACK_ALLOCATOR``
- ``CONFIGURE_TASK_STACK_DEALLOCATOR`` - ``CONFIGURE_TASK_STACK_DEALLOCATOR``
.. index:: CONFIGURE_TASK_STACK_DEALLOCATOR .. index:: CONFIGURE_TASK_STACK_DEALLOCATOR
.. index:: task stack deallocator .. index:: task stack deallocator
@ -106,8 +106,8 @@ DESCRIPTION:
NOTES: NOTES:
A correctly configured system must configure the following to be consistent: A correctly configured system must configure the following to be consistent:
- ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT`` - ``CONFIGURE_TASK_STACK_ALLOCATOR_INIT``
- ``CONFIGURE_TASK_STACK_ALLOCATOR`` - ``CONFIGURE_TASK_STACK_ALLOCATOR``
- ``CONFIGURE_TASK_STACK_DEALLOCATOR`` - ``CONFIGURE_TASK_STACK_DEALLOCATOR``