Forum Post: RE: configuring the syslink shared memory size in Linux

Hey, sudheer singh1.
This part is not clear for me as well,and im asking the same question. But i have found some information by far regarding process of sharing information about shared memory across the cores: there is a similar thread http://e2e.ti.com/support/embedded/tirtos/f/355/t/141150.aspx

"Actually, the method that's the most preferred and the easiest to do, is for you to not call SharedRegion_setEntry dynamically at all. If you want any extra SharedRegion, if you set it statically in the cfg file of the slave (any slave), it gets automatically pulled into and mapped into all processes that may run after that on A8, and you don't need to call SharedRegion_setEntry explicitly on the A8 at all. You can simply call SharedRegion_getHeap and start using the heap for your shared memory allocations. This is the method we suggest as the easiest to use."

So there is a call SharedRegion_setEntry which we can use to make info about shared memory in application only context.  Or we can run proc after slave,which has a statically configured shared memory entries via cfg file, and get info without calling SharedRegion_setEntry. But what will happen with such info if slave core will shutdown before others? such info becomes not correct, for example, heap for allocation messages becomes not accessible, isn't it?