<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style></head>
<body>
<body><p dir="ltr">+1</p><p dir="ltr">One odd thought.. Can we detect when objects which are not unlimited are configured that way?</p><div class="quote">On Apr 29, 2014 10:40 AM, Gedare Bloom <gedare@rtems.org> wrote:<br type="attribution"></div></body>
<font size="2"><div class="PlainText">Looks good to me.<br>
<br>
On Tue, Apr 29, 2014 at 10:57 AM, Ralf Kirchner<br>
<ralf.kirchner@embedded-brains.de> wrote:<br>
> Mark POSIX Keys and POSIX Key Value Pairs as supported.<br>
> Add list of unsupported object classes.<br>
> Add hint to unified work areas.<br>
> Add example.<br>
> ---<br>
> doc/user/conf.t | 40 ++++++++++++++++++++++++++++++++++++----<br>
> 1 Datei geändert, 36 Zeilen hinzugefügt(+), 4 Zeilen entfernt(-)<br>
><br>
> diff --git a/doc/user/conf.t b/doc/user/conf.t<br>
> index f0aa022..ef40480 100644<br>
> --- a/doc/user/conf.t<br>
> +++ b/doc/user/conf.t<br>
> @@ -355,6 +355,14 @@ software is unknown. In these situations users do not need to control<br>
> the size of the workspace very tightly because they just want to get<br>
> the new software to run; later they can tune the workspace size as needed.<br>
><br>
> +The following API-independent object classes can be configured in<br>
> +unlimited mode:<br>
> +<br>
> +@itemize @bullet<br>
> +@item POSIX Keys<br>
> +@item POSIX Key Value Pairs<br>
> +@end itemize<br>
> +<br>
> The following object classes in the Classic API can be configured in<br>
> unlimited mode:<br>
><br>
> @@ -377,7 +385,6 @@ configured in unlimited mode:<br>
> @item Threads<br>
> @item Mutexes<br>
> @item Condition Variables<br>
> -@item Keys<br>
> @item Timers<br>
> @item Message Queues<br>
> @item Message Queue Descriptors<br>
> @@ -387,9 +394,34 @@ configured in unlimited mode:<br>
> @item Spinlocks<br>
> @end itemize<br>
><br>
> -Due to how the POSIX object memory requirements are configured the<br>
> -unlimited object support does not provide unlimited size declarations<br>
> -for POSIX keys or queued signals.<br>
> +The following object classes can @strong{not} be configured in unlimited mode:<br>
> +@itemize @bullet<br>
> +@item Drivers<br>
> +@item File Descriptors<br>
> +@item User Extensions<br>
> +@item Queued Signals<br>
> +@end itemize<br>
> +<br>
> +Due to the memory requirements of unlimited objects it is strongly recommended<br>
> +to use them only in combination with the unified work areas. See<br>
> +@ref{Configuring a System Separate or Unified Work Areas} for more information<br>
> +on unified work areas.<br>
> +<br>
> +The following example demonstrates how the two simple configuration defines for<br>
> +unlimited objects and unified works areas can replace many seperate<br>
> +configuration defines for supported object classes:<br>
> +@example<br>
> +#define CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER<br>
> +#define CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER<br>
> +#define CONFIGURE_RTEMS_INIT_TASKS_TABLE<br>
> +<br>
> +#define CONFIGURE_UNIFIED_WORK_AREAS<br>
> +#define CONFIGURE_UNLIMITED_OBJECTS<br>
> +<br>
> +#define CONFIGURE_INIT<br>
> +<br>
> +#include <rtems/confdefs.h><br>
> +@end example<br>
><br>
> Users are cautioned that using unlimited objects is not recommended for<br>
> production software unless the dynamic growth is absolutely required. It<br>
> --<br>
> 1.7.10.4<br>
><br>
> _______________________________________________<br>
> rtems-devel mailing list<br>
> rtems-devel@rtems.org<br>
> <a href="http://www.rtems.org/mailman/listinfo/rtems-devel">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
<br>
_______________________________________________<br>
rtems-devel mailing list<br>
rtems-devel@rtems.org<br>
<a href="http://www.rtems.org/mailman/listinfo/rtems-devel">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
</div></font>
</body>
</html>