Lines Matching refs:memory

109 \autoref{f:opendata} shows mapping an open dataspace into a given memory window. The initialisation sets up the components for sample fault delegation in the system.  Note that the process server is acting as the memory manager. The paging could instead be implemented through a separate memory manager process.
198 In this example, the shared dataspace is implemented by the process server (acting as the memory manager) and is shared with a server. This is typical for a shared memory communication buffer.
405 A memory window should bookkeep its state, which vspace it belongs to, where and how long the memory segment is and the state of the memory window's contents. A memory window may be unmapped or mapped to a dataspace, and that dataspace may or may not be content initialised. In \refOS, the process server is the anonymous memory dataserver, so in \refOS the memory window data structure has extra bookkeeping information for the internal anonymous dataspace mapping state. Also, \refOS separates the memory window's size and offset into multiple windows.
421 A process control block data structure should bookkeep its address space (capability space and virtual memory space), its threads and the clients it is watching. \refOS also contains parameter buffers, notification ring buffers, the process operating system capabilities bitmask, the parent process's ID, the debug name and a number of other bookkeeping parameters.
462 A userland dataspace mapping data strucure must bookkeep its window, dataspace and session and the virtual address and size of the memory window segment.