1 | .. SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | .. Copyright (C) 2020, 2021 embedded brains GmbH (http://www.embedded-brains.de) |
---|
4 | .. Copyright (C) 1988, 2022 On-Line Applications Research Corporation (OAR) |
---|
5 | |
---|
6 | .. This file is part of the RTEMS quality process and was automatically |
---|
7 | .. generated. If you find something that needs to be fixed or |
---|
8 | .. worded better please post a report or patch to an RTEMS mailing list |
---|
9 | .. or raise a bug report: |
---|
10 | .. |
---|
11 | .. https://www.rtems.org/bugs.html |
---|
12 | .. |
---|
13 | .. For information on updating and regenerating please refer to the How-To |
---|
14 | .. section in the Software Requirements Engineering chapter of the |
---|
15 | .. RTEMS Software Engineering manual. The manual is provided as a part of |
---|
16 | .. a release. For development sources please refer to the online |
---|
17 | .. documentation at: |
---|
18 | .. |
---|
19 | .. https://docs.rtems.org |
---|
20 | |
---|
21 | .. Generated from spec:/acfg/if/group-posix |
---|
22 | |
---|
23 | POSIX API Configuration |
---|
24 | ======================= |
---|
25 | |
---|
26 | This section describes configuration options related to the POSIX API. Most |
---|
27 | POSIX API objects are available by default since RTEMS 5.1. The queued signals |
---|
28 | and timers are only available if RTEMS was built with the enable POSIX |
---|
29 | build configuration option. |
---|
30 | |
---|
31 | .. Generated from spec:/acfg/if/max-posix-keys |
---|
32 | |
---|
33 | .. raw:: latex |
---|
34 | |
---|
35 | \clearpage |
---|
36 | |
---|
37 | .. index:: CONFIGURE_MAXIMUM_POSIX_KEYS |
---|
38 | |
---|
39 | .. _CONFIGURE_MAXIMUM_POSIX_KEYS: |
---|
40 | |
---|
41 | CONFIGURE_MAXIMUM_POSIX_KEYS |
---|
42 | ---------------------------- |
---|
43 | |
---|
44 | .. rubric:: CONSTANT: |
---|
45 | |
---|
46 | ``CONFIGURE_MAXIMUM_POSIX_KEYS`` |
---|
47 | |
---|
48 | .. rubric:: OPTION TYPE: |
---|
49 | |
---|
50 | This configuration option is an integer define. |
---|
51 | |
---|
52 | .. rubric:: DEFAULT VALUE: |
---|
53 | |
---|
54 | The default value is 0. |
---|
55 | |
---|
56 | .. rubric:: DESCRIPTION: |
---|
57 | |
---|
58 | The value of this configuration option defines the maximum number of POSIX |
---|
59 | API Keys that can be concurrently active. |
---|
60 | |
---|
61 | .. rubric:: NOTES: |
---|
62 | |
---|
63 | This object class can be configured in unlimited allocation mode, see |
---|
64 | :ref:`ConfigUnlimitedObjects`. |
---|
65 | |
---|
66 | .. rubric:: CONSTRAINTS: |
---|
67 | |
---|
68 | The following constraints apply to this configuration option: |
---|
69 | |
---|
70 | * The value of the configuration option shall be greater than or equal to zero. |
---|
71 | |
---|
72 | * The value of the configuration option shall be less than or equal to 65535. |
---|
73 | |
---|
74 | * The value of the configuration option shall be less than or equal to a |
---|
75 | BSP-specific and application-specific value which depends on the size of the |
---|
76 | memory available to the application. |
---|
77 | |
---|
78 | * The value of the configuration option may be defined through |
---|
79 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
80 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
81 | satisfies all other constraints of the configuration option. |
---|
82 | |
---|
83 | .. Generated from spec:/acfg/if/max-posix-key-value-pairs |
---|
84 | |
---|
85 | .. raw:: latex |
---|
86 | |
---|
87 | \clearpage |
---|
88 | |
---|
89 | .. index:: CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS |
---|
90 | |
---|
91 | .. _CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS: |
---|
92 | |
---|
93 | CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS |
---|
94 | --------------------------------------- |
---|
95 | |
---|
96 | .. rubric:: CONSTANT: |
---|
97 | |
---|
98 | ``CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS`` |
---|
99 | |
---|
100 | .. rubric:: OPTION TYPE: |
---|
101 | |
---|
102 | This configuration option is an integer define. |
---|
103 | |
---|
104 | .. rubric:: DEFAULT VALUE: |
---|
105 | |
---|
106 | The default value is |
---|
107 | :ref:`CONFIGURE_MAXIMUM_POSIX_KEYS` * |
---|
108 | ( :ref:`CONFIGURE_MAXIMUM_TASKS` + |
---|
109 | :ref:`CONFIGURE_MAXIMUM_POSIX_THREADS` ). |
---|
110 | |
---|
111 | .. rubric:: DESCRIPTION: |
---|
112 | |
---|
113 | The value of this configuration option defines the maximum number of key |
---|
114 | value pairs used by POSIX API Keys that can be concurrently active. |
---|
115 | |
---|
116 | .. rubric:: NOTES: |
---|
117 | |
---|
118 | This object class can be configured in unlimited allocation mode, see |
---|
119 | :ref:`ConfigUnlimitedObjects`. |
---|
120 | |
---|
121 | A key value pair is created by :c:func:`pthread_setspecific` if the value |
---|
122 | is not `NULL <https://en.cppreference.com/w/c/types/NULL>`_, otherwise it is deleted. |
---|
123 | |
---|
124 | .. rubric:: CONSTRAINTS: |
---|
125 | |
---|
126 | The following constraints apply to this configuration option: |
---|
127 | |
---|
128 | * The value of the configuration option shall be greater than or equal to zero. |
---|
129 | |
---|
130 | * The value of the configuration option shall be less than or equal to 65535. |
---|
131 | |
---|
132 | * The value of the configuration option shall be less than or equal to a |
---|
133 | BSP-specific and application-specific value which depends on the size of the |
---|
134 | memory available to the application. |
---|
135 | |
---|
136 | * The value of the configuration option may be defined through |
---|
137 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
138 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
139 | satisfies all other constraints of the configuration option. |
---|
140 | |
---|
141 | .. Generated from spec:/acfg/if/max-posix-message-queues |
---|
142 | |
---|
143 | .. raw:: latex |
---|
144 | |
---|
145 | \clearpage |
---|
146 | |
---|
147 | .. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES |
---|
148 | |
---|
149 | .. _CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES: |
---|
150 | |
---|
151 | CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES |
---|
152 | -------------------------------------- |
---|
153 | |
---|
154 | .. rubric:: CONSTANT: |
---|
155 | |
---|
156 | ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES`` |
---|
157 | |
---|
158 | .. rubric:: OPTION TYPE: |
---|
159 | |
---|
160 | This configuration option is an integer define. |
---|
161 | |
---|
162 | .. rubric:: DEFAULT VALUE: |
---|
163 | |
---|
164 | The default value is 0. |
---|
165 | |
---|
166 | .. rubric:: DESCRIPTION: |
---|
167 | |
---|
168 | The value of this configuration option defines the maximum number of POSIX |
---|
169 | API Message Queues that can be concurrently active. |
---|
170 | |
---|
171 | .. rubric:: NOTES: |
---|
172 | |
---|
173 | This object class can be configured in unlimited allocation mode, see |
---|
174 | :ref:`ConfigUnlimitedObjects`. You have to account for the memory used to |
---|
175 | store the messages of each message queue, see |
---|
176 | :ref:`CONFIGURE_MESSAGE_BUFFER_MEMORY`. |
---|
177 | |
---|
178 | .. rubric:: CONSTRAINTS: |
---|
179 | |
---|
180 | The following constraints apply to this configuration option: |
---|
181 | |
---|
182 | * The value of the configuration option shall be greater than or equal to zero. |
---|
183 | |
---|
184 | * The value of the configuration option shall be less than or equal to 65535. |
---|
185 | |
---|
186 | * The value of the configuration option shall be less than or equal to a |
---|
187 | BSP-specific and application-specific value which depends on the size of the |
---|
188 | memory available to the application. |
---|
189 | |
---|
190 | * The value of the configuration option shall be small enough so that the RTEMS |
---|
191 | Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
192 | overflow an integer of type `uintptr_t |
---|
193 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
194 | |
---|
195 | * The value of the configuration option may be defined through |
---|
196 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
197 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
198 | satisfies all other constraints of the configuration option. |
---|
199 | |
---|
200 | .. Generated from spec:/acfg/if/max-posix-queued-signals |
---|
201 | |
---|
202 | .. raw:: latex |
---|
203 | |
---|
204 | \clearpage |
---|
205 | |
---|
206 | .. index:: CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS |
---|
207 | |
---|
208 | .. _CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS: |
---|
209 | |
---|
210 | CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS |
---|
211 | -------------------------------------- |
---|
212 | |
---|
213 | .. rubric:: CONSTANT: |
---|
214 | |
---|
215 | ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS`` |
---|
216 | |
---|
217 | .. rubric:: OPTION TYPE: |
---|
218 | |
---|
219 | This configuration option is an integer define. |
---|
220 | |
---|
221 | .. rubric:: DEFAULT VALUE: |
---|
222 | |
---|
223 | The default value is 0. |
---|
224 | |
---|
225 | .. rubric:: DESCRIPTION: |
---|
226 | |
---|
227 | The value of this configuration option defines the maximum number of POSIX |
---|
228 | API Queued Signals that can be concurrently active. |
---|
229 | |
---|
230 | .. rubric:: NOTES: |
---|
231 | |
---|
232 | Unlimited objects are not available for queued signals. |
---|
233 | |
---|
234 | Queued signals are only available if RTEMS was built with the POSIX API |
---|
235 | build configuration option enabled. |
---|
236 | |
---|
237 | .. rubric:: CONSTRAINTS: |
---|
238 | |
---|
239 | The following constraints apply to this configuration option: |
---|
240 | |
---|
241 | * The value of the configuration option shall be greater than or equal to zero. |
---|
242 | |
---|
243 | * The value of the configuration option shall be less than or equal to a |
---|
244 | BSP-specific and application-specific value which depends on the size of the |
---|
245 | memory available to the application. |
---|
246 | |
---|
247 | * The value of the configuration option shall be small enough so that the RTEMS |
---|
248 | Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
249 | overflow an integer of type `uintptr_t |
---|
250 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
251 | |
---|
252 | * The value of the configuration option shall be zero if the POSIX API is not |
---|
253 | enabled (e.g. RTEMS was built without the ``RTEMS_POSIX_API = True`` build |
---|
254 | configuration option). Otherwise a compile time error in the configuration |
---|
255 | file will occur. |
---|
256 | |
---|
257 | .. Generated from spec:/acfg/if/max-posix-semaphores |
---|
258 | |
---|
259 | .. raw:: latex |
---|
260 | |
---|
261 | \clearpage |
---|
262 | |
---|
263 | .. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES |
---|
264 | |
---|
265 | .. _CONFIGURE_MAXIMUM_POSIX_SEMAPHORES: |
---|
266 | |
---|
267 | CONFIGURE_MAXIMUM_POSIX_SEMAPHORES |
---|
268 | ---------------------------------- |
---|
269 | |
---|
270 | .. rubric:: CONSTANT: |
---|
271 | |
---|
272 | ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES`` |
---|
273 | |
---|
274 | .. rubric:: OPTION TYPE: |
---|
275 | |
---|
276 | This configuration option is an integer define. |
---|
277 | |
---|
278 | .. rubric:: DEFAULT VALUE: |
---|
279 | |
---|
280 | The default value is 0. |
---|
281 | |
---|
282 | .. rubric:: DESCRIPTION: |
---|
283 | |
---|
284 | The value of this configuration option defines the maximum number of POSIX |
---|
285 | API Named Semaphores that can be concurrently active. |
---|
286 | |
---|
287 | .. rubric:: NOTES: |
---|
288 | |
---|
289 | This object class can be configured in unlimited allocation mode, see |
---|
290 | :ref:`ConfigUnlimitedObjects`. |
---|
291 | |
---|
292 | Named semaphores are created with :c:func:`sem_open`. Semaphores |
---|
293 | initialized with :c:func:`sem_init` are not affected by this |
---|
294 | configuration option since the storage space for these semaphores is |
---|
295 | user-provided. |
---|
296 | |
---|
297 | .. rubric:: CONSTRAINTS: |
---|
298 | |
---|
299 | The following constraints apply to this configuration option: |
---|
300 | |
---|
301 | * The value of the configuration option shall be greater than or equal to zero. |
---|
302 | |
---|
303 | * The value of the configuration option shall be less than or equal to 65535. |
---|
304 | |
---|
305 | * The value of the configuration option shall be less than or equal to a |
---|
306 | BSP-specific and application-specific value which depends on the size of the |
---|
307 | memory available to the application. |
---|
308 | |
---|
309 | * The value of the configuration option shall be small enough so that the RTEMS |
---|
310 | Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
311 | overflow an integer of type `uintptr_t |
---|
312 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
313 | |
---|
314 | * The value of the configuration option may be defined through |
---|
315 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
316 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
317 | satisfies all other constraints of the configuration option. |
---|
318 | |
---|
319 | .. Generated from spec:/acfg/if/max-posix-shms |
---|
320 | |
---|
321 | .. raw:: latex |
---|
322 | |
---|
323 | \clearpage |
---|
324 | |
---|
325 | .. index:: CONFIGURE_MAXIMUM_POSIX_SHMS |
---|
326 | |
---|
327 | .. _CONFIGURE_MAXIMUM_POSIX_SHMS: |
---|
328 | |
---|
329 | CONFIGURE_MAXIMUM_POSIX_SHMS |
---|
330 | ---------------------------- |
---|
331 | |
---|
332 | .. rubric:: CONSTANT: |
---|
333 | |
---|
334 | ``CONFIGURE_MAXIMUM_POSIX_SHMS`` |
---|
335 | |
---|
336 | .. rubric:: OPTION TYPE: |
---|
337 | |
---|
338 | This configuration option is an integer define. |
---|
339 | |
---|
340 | .. rubric:: DEFAULT VALUE: |
---|
341 | |
---|
342 | The default value is 0. |
---|
343 | |
---|
344 | .. rubric:: DESCRIPTION: |
---|
345 | |
---|
346 | The value of this configuration option defines the maximum number of POSIX |
---|
347 | API Shared Memory objects that can be concurrently active. |
---|
348 | |
---|
349 | .. rubric:: NOTES: |
---|
350 | |
---|
351 | This object class can be configured in unlimited allocation mode, see |
---|
352 | :ref:`ConfigUnlimitedObjects`. |
---|
353 | |
---|
354 | .. rubric:: CONSTRAINTS: |
---|
355 | |
---|
356 | The following constraints apply to this configuration option: |
---|
357 | |
---|
358 | * The value of the configuration option shall be greater than or equal to zero. |
---|
359 | |
---|
360 | * The value of the configuration option shall be less than or equal to 65535. |
---|
361 | |
---|
362 | * The value of the configuration option shall be less than or equal to a |
---|
363 | BSP-specific and application-specific value which depends on the size of the |
---|
364 | memory available to the application. |
---|
365 | |
---|
366 | * The value of the configuration option shall be small enough so that the RTEMS |
---|
367 | Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
368 | overflow an integer of type `uintptr_t |
---|
369 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
370 | |
---|
371 | * The value of the configuration option may be defined through |
---|
372 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
373 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
374 | satisfies all other constraints of the configuration option. |
---|
375 | |
---|
376 | .. Generated from spec:/acfg/if/max-posix-threads |
---|
377 | |
---|
378 | .. raw:: latex |
---|
379 | |
---|
380 | \clearpage |
---|
381 | |
---|
382 | .. index:: CONFIGURE_MAXIMUM_POSIX_THREADS |
---|
383 | |
---|
384 | .. _CONFIGURE_MAXIMUM_POSIX_THREADS: |
---|
385 | |
---|
386 | CONFIGURE_MAXIMUM_POSIX_THREADS |
---|
387 | ------------------------------- |
---|
388 | |
---|
389 | .. rubric:: CONSTANT: |
---|
390 | |
---|
391 | ``CONFIGURE_MAXIMUM_POSIX_THREADS`` |
---|
392 | |
---|
393 | .. rubric:: OPTION TYPE: |
---|
394 | |
---|
395 | This configuration option is an integer define. |
---|
396 | |
---|
397 | .. rubric:: DEFAULT VALUE: |
---|
398 | |
---|
399 | The default value is 0. |
---|
400 | |
---|
401 | .. rubric:: DESCRIPTION: |
---|
402 | |
---|
403 | The value of this configuration option defines the maximum number of POSIX |
---|
404 | API Threads that can be concurrently active. |
---|
405 | |
---|
406 | .. rubric:: NOTES: |
---|
407 | |
---|
408 | This object class can be configured in unlimited allocation mode, see |
---|
409 | :ref:`ConfigUnlimitedObjects`. |
---|
410 | |
---|
411 | This calculations for the required memory in the RTEMS Workspace for threads |
---|
412 | assume that each thread has a minimum stack size and has floating point |
---|
413 | support enabled. The configuration option :ref:`CONFIGURE_EXTRA_TASK_STACKS` is used |
---|
414 | to specify thread stack requirements **above** the minimum size required. |
---|
415 | |
---|
416 | The maximum number of Classic API Tasks is specified by |
---|
417 | :ref:`CONFIGURE_MAXIMUM_TASKS`. |
---|
418 | |
---|
419 | All POSIX threads have floating point enabled. |
---|
420 | |
---|
421 | .. rubric:: CONSTRAINTS: |
---|
422 | |
---|
423 | The following constraints apply to this configuration option: |
---|
424 | |
---|
425 | * The value of the configuration option shall be greater than or equal to zero. |
---|
426 | |
---|
427 | * The value of the configuration option shall be less than or equal to 65535. |
---|
428 | |
---|
429 | * The value of the configuration option shall be less than or equal to a |
---|
430 | BSP-specific and application-specific value which depends on the size of the |
---|
431 | memory available to the application. |
---|
432 | |
---|
433 | * The value of the configuration option shall be small enough so that the task |
---|
434 | stack space calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
435 | overflow an integer of type `uintptr_t |
---|
436 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
437 | |
---|
438 | .. Generated from spec:/acfg/if/max-posix-timers |
---|
439 | |
---|
440 | .. raw:: latex |
---|
441 | |
---|
442 | \clearpage |
---|
443 | |
---|
444 | .. index:: CONFIGURE_MAXIMUM_POSIX_TIMERS |
---|
445 | |
---|
446 | .. _CONFIGURE_MAXIMUM_POSIX_TIMERS: |
---|
447 | |
---|
448 | CONFIGURE_MAXIMUM_POSIX_TIMERS |
---|
449 | ------------------------------ |
---|
450 | |
---|
451 | .. rubric:: CONSTANT: |
---|
452 | |
---|
453 | ``CONFIGURE_MAXIMUM_POSIX_TIMERS`` |
---|
454 | |
---|
455 | .. rubric:: OPTION TYPE: |
---|
456 | |
---|
457 | This configuration option is an integer define. |
---|
458 | |
---|
459 | .. rubric:: DEFAULT VALUE: |
---|
460 | |
---|
461 | The default value is 0. |
---|
462 | |
---|
463 | .. rubric:: DESCRIPTION: |
---|
464 | |
---|
465 | The value of this configuration option defines the maximum number of POSIX |
---|
466 | API Timers that can be concurrently active. |
---|
467 | |
---|
468 | .. rubric:: NOTES: |
---|
469 | |
---|
470 | This object class can be configured in unlimited allocation mode, see |
---|
471 | :ref:`ConfigUnlimitedObjects`. |
---|
472 | |
---|
473 | Timers are only available if RTEMS was built with the POSIX API build |
---|
474 | configuration option enabled. |
---|
475 | |
---|
476 | .. rubric:: CONSTRAINTS: |
---|
477 | |
---|
478 | The following constraints apply to this configuration option: |
---|
479 | |
---|
480 | * The value of the configuration option shall be greater than or equal to zero. |
---|
481 | |
---|
482 | * The value of the configuration option shall be less than or equal to 65535. |
---|
483 | |
---|
484 | * The value of the configuration option shall be less than or equal to a |
---|
485 | BSP-specific and application-specific value which depends on the size of the |
---|
486 | memory available to the application. |
---|
487 | |
---|
488 | * The value of the configuration option may be defined through |
---|
489 | :c:func:`rtems_resource_unlimited` the enable unlimited objects for the |
---|
490 | object class, if the value passed to :c:func:`rtems_resource_unlimited` |
---|
491 | satisfies all other constraints of the configuration option. |
---|
492 | |
---|
493 | * The value of the configuration option shall be zero if the POSIX API is not |
---|
494 | enabled (e.g. RTEMS was built without the ``RTEMS_POSIX_API = True`` build |
---|
495 | configuration option). Otherwise a compile time error in the configuration |
---|
496 | file will occur. |
---|
497 | |
---|
498 | .. Generated from spec:/acfg/if/min-posix-thread-stack-size |
---|
499 | |
---|
500 | .. raw:: latex |
---|
501 | |
---|
502 | \clearpage |
---|
503 | |
---|
504 | .. index:: CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE |
---|
505 | .. index:: minimum POSIX thread stack size |
---|
506 | |
---|
507 | .. _CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE: |
---|
508 | |
---|
509 | CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE |
---|
510 | ----------------------------------------- |
---|
511 | |
---|
512 | .. rubric:: CONSTANT: |
---|
513 | |
---|
514 | ``CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE`` |
---|
515 | |
---|
516 | .. rubric:: OPTION TYPE: |
---|
517 | |
---|
518 | This configuration option is an integer define. |
---|
519 | |
---|
520 | .. rubric:: DEFAULT VALUE: |
---|
521 | |
---|
522 | The default value is two times the value of |
---|
523 | :ref:`CONFIGURE_MINIMUM_TASK_STACK_SIZE`. |
---|
524 | |
---|
525 | .. rubric:: DESCRIPTION: |
---|
526 | |
---|
527 | The value of this configuration option defines the minimum stack size in |
---|
528 | bytes for every POSIX thread in the system. |
---|
529 | |
---|
530 | .. rubric:: CONSTRAINTS: |
---|
531 | |
---|
532 | The following constraints apply to this configuration option: |
---|
533 | |
---|
534 | * The value of the configuration option shall be small enough so that the task |
---|
535 | stack space calculation carried out by ``<rtems/confdefs.h>`` does not |
---|
536 | overflow an integer of type `uintptr_t |
---|
537 | <https://en.cppreference.com/w/c/types/integer>`_. |
---|
538 | |
---|
539 | * The value of the configuration option shall be greater than or equal to a |
---|
540 | BSP-specific and application-specific minimum value. |
---|