- There's a new message that describes the physical layout of a shared memory object in one transaction
(as opposed to multiple calls to
mem_offset())
and without the need to map the object (to avoid wasting time and virtual address space)
- There's now an enhanced
mmap()
protocol between the memory manager and a server that allows the server to respond to a mmap()
call by specifying a shared memory object and an offset which the client should be mapping.
This should eliminate many of the current use cases for mmap_peer(),
especially with direct physical addresses.
For information about these, see
“Handling mmap() messages”
in the “Handling Other Messages” chapter of Writing a Resource Manager.