El 03/07/2014 10:24, Jorge Bellon escribió:
Hi Ion, Thank you for the info.
The use case would be to manage a memory pool allocated on a remote node.
This would be used by a run-time library for distributed programming. It would allocate a memory region and manage this memory from another node, so that we can perform operations with that piece of memory (allocate portions, transfer data, etc.) without the intervention of the local node.
Why can't you put the manager in the remote node? The manager also needs
to allocate memory for indexes that track the position of named/unique
objects and that memory comes from the memory region also used to
construct objects. If you don't need named objects you can use a null
index to minimize used memory.
Do you need to shared this remote node memory between processes? If you
only use remote memory from a single process you can speed things a bit
using raw pointers:
typedef basic_managed_external_buffer <
char,
rbtree_best_fit