blob: 11f4413c4bda232d0d9b6769425d36874a1f75cf (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
appl-config-option-type: integer
copyrights:
- Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
default-value: 0
description: |
The value of this configuration option defines the maximum number of Classic
API Tasks that can be concurrently active.
enabled-by: true
index-entries: []
interface-type: appl-config-option
links:
- role: requirement-refinement
uid: ../req/max-tasks
- role: appl-config-group-member
uid: group-classic
- role: constraint
uid: ../constraint/min-zero
- role: constraint
uid: ../constraint/max-obj
- role: constraint
uid: ../constraint/memory-size
- role: constraint
uid: ../constraint/stack-space
- role: constraint
uid: ../constraint/unlimited
name: CONFIGURE_MAXIMUM_TASKS
notes: |
This object class can be configured in unlimited allocation mode, see
${.:/document-reference/config-unlimited-objects}.
The calculations for the required memory in the RTEMS Workspace for tasks
assume that each task has a minimum stack size and has floating point
support enabled. The configuration option ${extra-task-stacks:/name} is used
to specify task stack requirements *above* the minimum size required.
The maximum number of POSIX threads is specified by
${max-posix-threads:/name}.
A future enhancement to ``<rtems/confdefs.h>`` could be to eliminate the
assumption that all tasks have floating point enabled. This would require
the addition of a new configuration parameter to specify the number of
tasks which enable floating point support.
type: interface
|
