[rtems-docs commit] c-user: Sort POSIX configuration options

Sebastian Huber sebh at rtems.org
Wed Aug 8 06:53:46 UTC 2018


Module:    rtems-docs
Branch:    master
Commit:    8fd9e62facbd0b781758a346095b7f6d0c183ce1
Changeset: http://git.rtems.org/rtems-docs/commit/?id=8fd9e62facbd0b781758a346095b7f6d0c183ce1

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Aug  7 08:04:28 2018 +0200

c-user: Sort POSIX configuration options

---

 c-user/configuring_a_system.rst | 120 ++++++++++++++++++++--------------------
 1 file changed, 60 insertions(+), 60 deletions(-)

diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index 4b5fe52..a22d321 100644
--- a/c-user/configuring_a_system.rst
+++ b/c-user/configuring_a_system.rst
@@ -1055,15 +1055,15 @@ The parameters in this section are used to configure resources for the RTEMS
 POSIX API.  They are only relevant if the POSIX API is enabled at configure
 time using the ``--enable-posix`` option.
 
-.. index:: CONFIGURE_MAXIMUM_POSIX_THREADS
+.. index:: CONFIGURE_MAXIMUM_POSIX_KEYS
 
-.. _CONFIGURE_MAXIMUM_POSIX_THREADS:
+.. _CONFIGURE_MAXIMUM_POSIX_KEYS:
 
-CONFIGURE_MAXIMUM_POSIX_THREADS
--------------------------------
+CONFIGURE_MAXIMUM_POSIX_KEYS
+----------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_THREADS``
+    ``CONFIGURE_MAXIMUM_POSIX_KEYS``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1075,34 +1075,21 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_THREADS`` is the maximum number of POSIX API
-    Threads that can be concurrently active.
+    ``CONFIGURE_MAXIMUM_POSIX_KEYS`` is the maximum number of POSIX API Keys
+    that can be concurrently active.
 
 NOTES:
     This object class can be configured in unlimited allocation mode.
 
-    This calculations for the required memory in the RTEMS Workspace for
-    threads assume that each thread has a minimum stack size and has floating
-    point support enabled.  The configuration parameter
-    ``CONFIGURE_EXTRA_TASK_STACKS`` is used to specify thread stack
-    requirements *ABOVE* the minimum size required.  See :ref:`Reserve
-    Task/Thread Stack Memory Above Minimum` for more information about
-    ``CONFIGURE_EXTRA_TASK_STACKS``.
-
-    The maximum number of Classic API Tasks is specified by
-    ``CONFIGURE_MAXIMUM_TASKS``.
-
-    All POSIX threads have floating point enabled.
-
-.. index:: CONFIGURE_MAXIMUM_POSIX_KEYS
+.. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
 
-.. _CONFIGURE_MAXIMUM_POSIX_KEYS:
+.. _CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES:
 
-CONFIGURE_MAXIMUM_POSIX_KEYS
-----------------------------
+CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
+--------------------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_KEYS``
+    ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1114,21 +1101,21 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_KEYS`` is the maximum number of POSIX API Keys
-    that can be concurrently active.
+    ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES`` is the maximum number of POSIX
+    API Message Queues that can be concurrently active.
 
 NOTES:
     This object class can be configured in unlimited allocation mode.
 
-.. index:: CONFIGURE_MAXIMUM_POSIX_TIMERS
+.. index:: CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
 
-.. _CONFIGURE_MAXIMUM_POSIX_TIMERS:
+.. _CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS:
 
-CONFIGURE_MAXIMUM_POSIX_TIMERS
-------------------------------
+CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
+--------------------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_TIMERS``
+    ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1140,21 +1127,21 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_TIMERS`` is the maximum number of POSIX API
-    Timers that can be concurrently active.
+    ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS`` is the maximum number of POSIX
+    API Queued Signals that can be concurrently active.
 
 NOTES:
-    This object class can be configured in unlimited allocation mode.
+    None.
 
-.. index:: CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
+.. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
 
-.. _CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS:
+.. _CONFIGURE_MAXIMUM_POSIX_SEMAPHORES:
 
-CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
---------------------------------------
+CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
+----------------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS``
+    ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1166,21 +1153,24 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS`` is the maximum number of POSIX
-    API Queued Signals that can be concurrently active.
+    ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES`` is the maximum number of POSIX API
+    Named Semaphores that can be concurrently active.  Named semaphores are
+    created with ``sem_open()``.  Semaphores initialized with ``sem_init()``
+    are not affected by this configuration option since the storage space for
+    these semaphores is user-provided.
 
 NOTES:
     None.
 
-.. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
+.. index:: CONFIGURE_MAXIMUM_POSIX_TIMERS
 
-.. _CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES:
+.. _CONFIGURE_MAXIMUM_POSIX_TIMERS:
 
-CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
---------------------------------------
+CONFIGURE_MAXIMUM_POSIX_TIMERS
+------------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES``
+    ``CONFIGURE_MAXIMUM_POSIX_TIMERS``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1192,21 +1182,21 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES`` is the maximum number of POSIX
-    API Message Queues that can be concurrently active.
+    ``CONFIGURE_MAXIMUM_POSIX_TIMERS`` is the maximum number of POSIX API
+    Timers that can be concurrently active.
 
 NOTES:
     This object class can be configured in unlimited allocation mode.
 
-.. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
+.. index:: CONFIGURE_MAXIMUM_POSIX_THREADS
 
-.. _CONFIGURE_MAXIMUM_POSIX_SEMAPHORES:
+.. _CONFIGURE_MAXIMUM_POSIX_THREADS:
 
-CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
-----------------------------------
+CONFIGURE_MAXIMUM_POSIX_THREADS
+-------------------------------
 
 CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES``
+    ``CONFIGURE_MAXIMUM_POSIX_THREADS``
 
 DATA TYPE:
     Unsigned integer (``uint32_t``).
@@ -1218,14 +1208,24 @@ DEFAULT VALUE:
     The default value is 0.
 
 DESCRIPTION:
-    ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES`` is the maximum number of POSIX API
-    Named Semaphores that can be concurrently active.  Named semaphores are
-    created with ``sem_open()``.  Semaphores initialized with ``sem_init()``
-    are not affected by this configuration option since the storage space for
-    these semaphores is user-provided.
+    ``CONFIGURE_MAXIMUM_POSIX_THREADS`` is the maximum number of POSIX API
+    Threads that can be concurrently active.
 
 NOTES:
-    None.
+    This object class can be configured in unlimited allocation mode.
+
+    This calculations for the required memory in the RTEMS Workspace for
+    threads assume that each thread has a minimum stack size and has floating
+    point support enabled.  The configuration parameter
+    ``CONFIGURE_EXTRA_TASK_STACKS`` is used to specify thread stack
+    requirements *ABOVE* the minimum size required.  See :ref:`Reserve
+    Task/Thread Stack Memory Above Minimum` for more information about
+    ``CONFIGURE_EXTRA_TASK_STACKS``.
+
+    The maximum number of Classic API Tasks is specified by
+    ``CONFIGURE_MAXIMUM_TASKS``.
+
+    All POSIX threads have floating point enabled.
 
 POSIX Initialization Threads Table Configuration
 ================================================




More information about the vc mailing list