The whole point is that a system block is 4K but the only operation that needs memory is a cctalk operation these are queued here in the server. A cctalk operation is 536-bytes so seven of these at a time are requested from the system. This will hopefully reduce memory fragmentation of available free memory to Linux.
NOTE from man page on malloc & free: In case Linux is employed under circumstances where it would be less desirable to suddenly lose some randomly picked processes, and moreover the kernel version is sufficiently recent, one can switch off this over-committing behavior using a command like: # echo 2 > /proc/sys/vm/overcommit_memory
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.
Functions | |
| void | cctm_Initialise (void) |
| Initialise the cctalk memory manager. | |
| void | cctm_Shutdown (void) |
| close down the memory manager. | |
| tsCCTALK_OPERATION * | cctm_MallocOp (void) |
| Get a packet from the free list and return it. | |
| void | cctm_FreeOp (tsCCTALK_OPERATION *pCctOp) |
| Free a cctalk operation. | |
|
|
Free a cctalk operation. Return a cctalk operation to the free list call when finished with a cctalk operation.
History |
|
|
Initialise the cctalk memory manager. Set up the memory manager this is going to be a block manager it is not overly complicated but there are a few complications
History |
Here is the call graph for this function:

|
|
Get a packet from the free list and return it. Called by the server to allocate a cctalk operation that can be used to store an cctalk operation. A cctalk structure is taken from the free list and returned to the calling process.
History |
Here is the call graph for this function:

|
|
close down the memory manager.
History |
1.3.6