blob: 8d57342c488f75dcd602647bbf3a4288d7e9fa6a (
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
|
SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
appl-config-option-type: feature
copyrights:
- Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
default: |
If this configuration option is undefined, then there will be separate memory
pools for the RTEMS Workspace and C Program Heap.
description: |
In case this configuration option is defined, then the RTEMS Workspace and
the C Program Heap will be one pool of memory.
enabled-by: true
index-entries:
- unified work areas
- separate work areas
- RTEMS Workspace
- C Program Heap
interface-type: appl-config-option
links:
- role: appl-config-group-member
uid: group-general
name: CONFIGURE_UNIFIED_WORK_AREAS
notes: |
Having separate pools does have some advantages in the event a task blows a
stack or writes outside its memory area. However, in low memory systems the
overhead of the two pools plus the potential for unused memory in either
pool is very undesirable.
In high memory environments, this is desirable when you want to use the
${.:/document-reference/config-unlimited-objects} option. You will be able to create objects
until you run out of all available memory rather then just until you run out
of RTEMS Workspace.
text: ''
type: interface
|
