RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

2008-09-17 Joel Sherrill <joel.sherrill@oarcorp.com>

Browse Source 
* user/conf.t: Add support for optionally having a unified work area.
	In other words, the RTEMS Workspace and C Program Heap are the same
	pool of memory.
This commit is contained in:
Joel Sherrill
2008-09-17 18:37:46 +00:00
parent d4331a291b
commit 2f3e2e0eaa
2 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/user/conf.t
View File

@@ -210,6 +210,20 @@ address of the RTEMS RAM Workspace. By default, this value
is NULL indicating that the BSP is to determine the location
of the RTEMS RAM Workspace.
@findex CONFIGURE_UNIFIED_WORK_AREAS
@item @code{CONFIGURE_UNIFIED_WORK_AREAS} configures RTEMS to use a
single memory pool for the RTEMS Workspace and C Program Heap. If not
defined, there will be separate memory pools for the RTEMS Workspace and
C Program Heap. Having separate pools does haved 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
RTEMS "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.
@item @code{CONFIGURE_MICROSECONDS_PER_TICK} is the length
of time between clock ticks. By default, this is set to
10000 microseconds.