Lines Matching refs:of

8 creation of a dispatch source of type `DISPATCH_SOURCE_TYPE_MEMORYPRESSURE`.
21 …| `DISPATCH_MEMORYPRESSURE_PROC_LIMIT_WARN`     | Process is within 100 MB of its memory limit.   …
27 `memorystatus_vm_pressure_level`. There are 5 distinct levels of pressure:
41 The VM monitors the amount of "available memory" , which comprises the following:
48 In other words, `AVAILABLE_NON_COMPRESSED_MEMORY` tracks all of the memory on
69 …AVAILABLE_MEMORY`  | `0.5 * AVAILABLE_MEMORY`  | Initiate minor-compaction of compressed segments.…
70 …E_MEMORY`  | `0.4 * AVAILABLE_MEMORY`  | Begin major-compaction & swapping of compressed segments.…
81 The jetsam control loop monitors a different measure of "available" memory
83 This available page count is the subset of `AVAILABLE_NON_COMPRESSED_MEMORY`
85 purgeable). Jetsam monitors the ratio of these fully-reclaimable pages to
89 The design goals of jetsam and vm_pressure can be thought of in the following
92 Jetsam attempts to maintain a sufficiently large pool of
94 need not be overly large; thus jetsam thresholds are generally on the order of
95 5%/10%/15% of max_mem.
97 Conversely, vm_pressure attempts to maintain the amount of memory available to
98 the working set of processes. On a healthy system, this should be at least a
99 majority of the memory not otherwise wired down or stolen by the operating