From f75e0bee4811bb33210a48fe573716c0bb19d5a1 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Tue, 17 Mar 2020 15:04:37 +0100 Subject: c-user: Fix format Update #3836. --- c-user/config/general.rst | 54 +++++++++++++++++++------------------- c-user/config/task-stack-alloc.rst | 18 ++++++------- 2 files changed, 36 insertions(+), 36 deletions(-) diff --git a/c-user/config/general.rst b/c-user/config/general.rst index ab86e4b..2170428 100644 --- a/c-user/config/general.rst +++ b/c-user/config/general.rst @@ -201,37 +201,37 @@ DEFAULT VALUE: to 255. DESCRIPTION: - For the schedulers + For the schedulers - * :ref:`SchedulerPriority`, which is the default in uniprocessor - configurations and can be configured through the - :ref:`CONFIGURE_SCHEDULER_PRIORITY` configuration option, + * :ref:`SchedulerPriority`, which is the default in uniprocessor + configurations and can be configured through the + :ref:`CONFIGURE_SCHEDULER_PRIORITY` configuration option, - * :ref:`SchedulerSMPPriority` which can be configured through the - :ref:`CONFIGURE_SCHEDULER_PRIORITY_SMP` configuration option, and + * :ref:`SchedulerSMPPriority` which can be configured through the + :ref:`CONFIGURE_SCHEDULER_PRIORITY_SMP` configuration option, and - * :ref:`SchedulerSMPPriorityAffinity` which can be configured through the - :ref:`CONFIGURE_SCHEDULER_PRIORITY_AFFINITY_SMP` configuration option + * :ref:`SchedulerSMPPriorityAffinity` which can be configured through the + :ref:`CONFIGURE_SCHEDULER_PRIORITY_AFFINITY_SMP` configuration option - this configuration option specifies the maximum numeric priority of any task - for these schedulers and one less that the number of priority levels for - these schedulers. For all other schedulers provided by RTEMS, this - configuration option has no effect. + this configuration option specifies the maximum numeric priority of any task + for these schedulers and one less that the number of priority levels for + these schedulers. For all other schedulers provided by RTEMS, this + configuration option has no effect. NOTES: - The numerically greatest priority is the logically lowest priority in the - system and will thus be used by the IDLE task. + The numerically greatest priority is the logically lowest priority in the + system and will thus be used by the IDLE task. - Priority zero (0) is reserved for internal use by RTEMS and is not available - to applications. + Priority zero (0) is reserved for internal use by RTEMS and is not available + to applications. - Reducing the number of priorities through this configuration option reduces - the amount of memory allocated by the schedulers listed above. These - schedulers use a chain control structure per priority and this structure - 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 - priority levels (default), 48 bytes for 4 priority levels - (``CONFIGURE_MAXIMUM_PRIORITY == 3``). + Reducing the number of priorities through this configuration option reduces + the amount of memory allocated by the schedulers listed above. These + schedulers use a chain control structure per priority and this structure + 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 + priority levels (default), 48 bytes for 4 priority levels + (``CONFIGURE_MAXIMUM_PRIORITY == 3``). .. index:: CONFIGURE_MAXIMUM_PROCESSORS @@ -288,12 +288,12 @@ DEFAULT VALUE: `PTHREAD_SETNAME_NP(3) `_. DESCRIPTION: - This configuration parameter specifies the maximum thread name size - including the terminating `NUL` character. + This configuration parameter specifies the maximum thread name size + including the terminating `NUL` character. NOTES: - The size of the thread control block is increased by the maximum thread name - size. This configuration option is available since RTEMS 5.1. + The size of the thread control block is increased by the maximum thread name + size. This configuration option is available since RTEMS 5.1. .. index:: CONFIGURE_MEMORY_OVERHEAD diff --git a/c-user/config/task-stack-alloc.rst b/c-user/config/task-stack-alloc.rst index a96bbdc..8771ab7 100644 --- a/c-user/config/task-stack-alloc.rst +++ b/c-user/config/task-stack-alloc.rst @@ -38,11 +38,11 @@ DESCRIPTION: NOTES: 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 @@ -72,11 +72,11 @@ DESCRIPTION: NOTES: 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:: task stack deallocator @@ -106,8 +106,8 @@ DESCRIPTION: NOTES: 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`` -- cgit v1.2.3