Dynamic memory management in an rdma context

A computer-based system for dynamically managing memory to support one or more processes executing in a remote direct memory access environment, the system comprising:

• a memory for electronically storing executable processing instructions;
• a processor for executing at least one process based upon the executable processing instructions;
• a descriptor module for causing the processor to store a descriptor in a shared descriptor table, the descriptor uniquely corresponding to a block of the memory allocated to a heap;
• and
• a registration module configured to respond to a process request for an allocation of a portion of the block of memory from the heap by determining whether the process has an existing registration for the block of memory with an application program interface, and if the process has no existing registration, storing a registration corresponding to the block of memory in a private registration table of the process, the registration module being further configured to remove the registration from the registration table in response to the process releasing the allocated portion of the block of memory to an operating system executed by the processor and de-registering with the application program interface;
• wherein, when the block of memory is released to the operating system, other registrations corresponding to the block of memory in other private registration tables of other processes remain in the other registration tables.

A computer-readable storage having embedded therein computer-executable code that, when loaded to and executed by the computer, cause the computer to perform the steps of:

• inserting a descriptor in a shared descriptor table, the descriptor corresponding to a block of memory allocated to a heap by an operating system;
• in response to allocating a portion of the block of memory from the heap to a process, determining whether the process has an existing registration with an application program interface for the block of memory, and if the process has no existing registration, registering the process with the application program interface and storing a registration corresponding to the block of memory in a private registration table of the process;
• and
• in response to the process releasing the allocated portion of the block of memory to the operating system and de-registering with the application program interface, removing the registration from the registration table;
• wherein, when the block of memory is released to the operating system, other registrations corresponding to the block of memory in other private registration tables of other processes remain in the other registration tables.