Server Interface - Report to memory manager that a previous consistency control request has been handled.
kern_return_t memory_object_lock_completed (memory_object_t reply_port, memory_object_control_t memory_control, vm_offset_t offset, vm_size_t length); kern_return_t seqnos_memory_object_lock_completed (memory_object_t reply_port, mach_port_seqno_t seqno, memory_object_control_t memory_control, vm_offset_t offset, vm_size_t length);
A memory_object_lock_completed function is called as the result of a kernel message confirming the kernel's action in response to a memory_object_lock_request call from the memory manager. The memory manager can use the memory_object_lock_request call to:
When the kernel completes the requested actions, it calls memory_object_lock_completed (asynchronously) using the port explicitly provided in the memory_object_lock_request call. Because the memory manager cannot know which pages have been modified, or even which pages remain in the cache, it cannot know how many pages will be written back in response to a memory_object_lock_request call. Receiving the memory_object_lock_completed call is the only sure means of detecting completion. The completion call includes the offset and length values from the consistency request to distinguish it from other consistency requests.
Only generic errors apply.
Functions: memory_object_lock_request, memory_object_server, seqnos_memory_object_server.