Lines Matching refs:that

17 Depending on the resource, there are a variety of actions that memorystatus might take.
20 for killing processes that go over their per-process memory limits.
41   (that should be in `bsd/kern/kern_memorystatus_policy.c`), but that's a recent refactor so
58 …d/kern/kern_memorystatus.c`). However, there are some synchronous actions that happen on other thr…
64 …sd/kern/kern_memorystatus_policy.c`) for the conditions that trigger specific actions. Note that w…
67 Notice that the memorystatus thread does not explicitly check why it was woken up.
111 …ystatus_available_pages` metric. This metric reflects the number of pages that memorystatus thinks…
113 … it's defined as `pageable_external + free + secluded_over_target + purgeable`. Breaking that down:
116 …ded_mem_mb`. Secluded memory is a special pool of memory that's intended for the camera so that it…
117 …that the VM can treat the contents of a range of pages as volatile and quickly free the backing pa…
130 \*Note that the memorystatus pressure threshold does *not* determine the "system memory pressure le…
135 This section lists the threads that comprise the memorystatus subsystem. More details on each threa…
158 to freeze up to that many processes before blocking. `memorystatus_pick_freeze_count_for_wakeup` re…
170 The memorystatus subsystem provides a snapshot mechanism so that
172 a snapshot of the system at the time that memorystatus performed
175 **NB**: Posting the snapshot just means sending a notification to userspace that the snapshot is re…
178 …t object. It reuses the snapshot struct definition but only contains apps that have been jetsammed.
180 …shot is also reset when dasd reads it. Note that it has to be separate from the OSAnalytics snapsh…