summaryrefslogtreecommitdiff
path: root/spec/if/acfg/max-tasks.yml
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2020-09-16 11:48:29 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2020-09-16 16:33:00 +0200
commit3bdf817950eadd75a2785b62220eb0b04533b9fd (patch)
treeed221c6de813e7a473e2882af6326bf2e5b44bd1 /spec/if/acfg/max-tasks.yml
parent724df1c5ef711c9399cd8c33b23aee40304d0332 (diff)
spec: Group items by component
Diffstat (limited to 'spec/if/acfg/max-tasks.yml')
-rw-r--r--spec/if/acfg/max-tasks.yml42
1 files changed, 0 insertions, 42 deletions
diff --git a/spec/if/acfg/max-tasks.yml b/spec/if/acfg/max-tasks.yml
deleted file mode 100644
index 86f97695..00000000
--- a/spec/if/acfg/max-tasks.yml
+++ /dev/null
@@ -1,42 +0,0 @@
-SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
-appl-config-option-type: integer
-constraints:
- max: 65535
- min: 0
-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: appl-config-group-member
- uid: group-classic
-- role: constraint
- uid: constraint-unlimited
-- role: constraint
- uid: constraint-stackspace
-- role: constraint
- uid: constraint-memsz
-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.
-text: ''
-type: interface