Changeset 2f3e2e0 in rtems


Ignore:
Timestamp:
Sep 17, 2008, 6:37:46 PM (11 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, master
Children:
bd5984de
Parents:
d4331a2
Message:

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

  • 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.
Location:
doc
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • doc/ChangeLog

    rd4331a2 r2f3e2e0  
     12008-09-17      Joel Sherrill <joel.sherrill@oarcorp.com>
     2
     3        * user/conf.t: Add support for optionally having a unified work area.
     4        In other words, the RTEMS Workspace and C Program Heap are the same
     5        pool of memory.
     6
    172008-09-09      Joel Sherrill <joel.sherrill@oarcorp.com>
    28
  • doc/user/conf.t

    rd4331a2 r2f3e2e0  
    210210is NULL indicating that the BSP is to determine the location
    211211of the RTEMS RAM Workspace.
     212
     213@findex CONFIGURE_UNIFIED_WORK_AREAS
     214@item @code{CONFIGURE_UNIFIED_WORK_AREAS} configures RTEMS to use a
     215single memory pool for the RTEMS Workspace and C Program Heap.  If not
     216defined, there will be separate memory pools for the RTEMS Workspace and
     217C Program Heap.  Having separate pools does haved some advantages in the
     218event a task blows a stack or writes outside its memory area. However,
     219in low memory systems the overhead of the two pools plus the potential
     220for unused memory in either pool is very undesirable.
     221
     222In high memory environments, this is desirable when you want to use the
     223RTEMS "unlimited" objects option.  You will be able to create objects
     224until you run out of all available memory rather then just until you
     225run out of RTEMS Workspace.
    212226
    213227@item @code{CONFIGURE_MICROSECONDS_PER_TICK} is the length
Note: See TracChangeset for help on using the changeset viewer.