umd/core/src/compiler/Memory.cpp
memory::MemoryResolver::MemoryResolver() :
    ast::GraphVisitor<engine_ast::Graph>(),
    m_useMemPool(false),
    m_useReusePooledMemory(false),
    m_useGreedyEviction(false),
    m_useCVSRAM(false),
    m_pools(NULL),
    m_localCVSRAM(NULL),
    m_localSDRAM(NULL),
    m_globalSDRAM(NULL),
    m_debug(false),
    m_inLocalPool()
{

}
//
// regarding memory-reuse:  the only place it makes sense to worry
// about re-using memory is within the pools.  outside of that we
// must leave the buffers in place; they can't be manipulated
// while the dla engine is working.
// further, it doesn't make much sense to bother with releasing
// global memory pooled items.  those are almost always
// content-bearing and so must be initalized at 0-time and
// thereafter no new buffers are created within it (transients
// are created in "local" memory).
// so, we really only need to worry about alloc/dealloc within
// the local sdram and cvsram pools.
//
//
regarding memory-reuse:  the only place it makes sense to worry
about re-using memory is within the pools.  outside of that we
must leave the buffers in place; they can't be manipulated
while the dla engine is working.
further, it doesn't make much sense to bother with releasing
global memory pooled items.  those are almost always
content-bearing and so must be initalized at 0-time and
thereafter no new buffers are created within it (transients
are created in "local" memory).
so, we really only need to worry about alloc/dealloc within
the local sdram and cvsram pools.
regarding memory - reuse : the only place it makes sense to worry about re - using memory is within the pools . outside of that we must leave the buffers in place ; they can ' t be manipulated while the dla engine is working . further it doesn ' t make much sense to bother with releasing global memory pooled items . those are almost always content - bearing and so must be initalized at 0 - time and thereafter no new buffers are created within it ( transients are created in " local " memory ) . so we really only need to worry about alloc / dealloc within the local sdram and cvsram pools .
memory::MemoryResolver::MemoryResolver() :
    ast::GraphVisitor<engine_ast::Graph>(),
    m_useMemPool(false),
    m_useReusePooledMemory(false),
    m_useGreedyEviction(false),
    m_useCVSRAM(false),
    m_pools(NULL),
    m_localCVSRAM(NULL),
    m_localSDRAM(NULL),
    m_globalSDRAM(NULL),
    m_debug(false),
    m_inLocalPool()
{
}
memory :: MemoryResolver :: MemoryResolver ( ) : ast :: GraphVisitor < engine_ast :: Graph > ( ) , m_useMemPool ( false ) , m_useReusePooledMemory ( false ) , m_useGreedyEviction ( false ) , m_useCVSRAM ( false ) , m_pools ( NULL ) , m_localCVSRAM ( NULL ) , m_localSDRAM ( NULL ) , m_globalSDRAM ( NULL ) , m_debug ( false ) , m_inLocalPool ( ) { }
regarding memory-reuse:  the only place it makes sense to worry
about re-using memory is within the pools.
regarding memory - reuse : the only place it makes sense to worry about re - using memory is within the pools .