1 <h2>memory_object_data_return
</h2>
4 <strong>Server Interface
</strong> - Return memory object data to the appropriate memory manager.
7 <strong>kern_return_t memory_object_data_return
</strong>
8 <strong>(memory_object_t
</strong> <var>memory_object
</var>,
9 <strong>memory_object_control_t
</strong> <var>memory_control
</var>,
10 <strong>vm_offset_t
</strong> <var>offset
</var>,
11 <strong>pointer_t
</strong> <var>data
</var>,
12 <strong>boolean_t
</strong> <var>dirty
</var>,
13 <strong>boolean_t
</strong> <var>kernel_copy
</var><strong>);
</strong>
16 <strong>kern_return_t seqnos_memory_object_data_return
</strong>
17 <strong>(memory_object_t
</strong> <var>memory_object
</var>,
18 <strong>mach_port_seqno_t
</strong> <var>seqno
</var>,
19 <strong>memory_object_control_t
</strong> <var>memory_control
</var>,
20 <strong>vm_offset_t
</strong> <var>offset
</var>,
21 <strong>pointer_t
</strong> <var>data
</var>,
22 <strong>boolean_t
</strong> <var>dirty
</var>,
23 <strong>boolean_t
</strong> <var>kernel_copy
</var><strong>);
</strong>
28 <dt> <var>memory_object
</var>
30 [in abstract-memory-object (receive) right]
32 object port that represents the memory object data.
37 The sequence number of this message relative to the abstract
40 <dt> <var>memory_control
</var>
42 [in memory-cache-control send right]
43 The memory cache control port
44 to be used for a response by the memory manager. If the memory
45 object has been supplied to more than one kernel, this parameter
46 identifies the kernel that is making the call.
48 <dt> <var>offset
</var>
51 The offset within the memory object.
55 [in pointer to dynamic array of bytes]
56 The data that has been evicted
57 from the physical memory cache.
62 If
<strong>TRUE
</strong>, the pages returned have been modified.
64 <dt> <var>kernel_copy
</var>
67 If
<strong>TRUE
</strong>, the kernel has kept a copy of the page.
71 A
<strong>memory_object_data_return
</strong> function is called as the
73 message providing the memory manager with data that has been evicted from the
74 physical memory cache.
76 The kernel writes back only data that has been modified or is precious. When
77 the memory manager no longer needs the data (for example, after the data has
78 been written to permanent storage), it should use
<strong>vm_deallocate
</strong>
83 The kernel can flush clean (that is, un-modified) non-precious
85 discretion. As a result, the memory manager cannot rely on the
87 copy of its data or even to provide notification that its data
90 The kernel may re-request the returned data at any time following this message
91 (including immediately).
92 <h3>RETURN VALUES
</h3>
94 Only generic errors apply.
95 <h3>RELATED INFORMATION
</h3>
98 <a href=
"memory_object_data_supply.html"><strong>memory_object_data_supply
</strong></a>,
99 <a href=
"vm_deallocate.html"><strong>vm_deallocate
</strong></a>,
100 <a href=
"memory_object_synchronize.html"><strong>memory_object_synchronize
</strong></a>,
101 <a href=
"memory_object_server.html"><strong>memory_object_server
</strong></a>,
102 <a href=
"SMO_server.html"><strong>seqnos_memory_object_server
</strong></a>.