Lines Matching refs:system

8 The xnu memorystatus subsystem is responsible for recovering the system when we're running dangerou…
18 One of the most common actions is to kill 1 or more processes in an attempt to recover the system.
19 In addition to monitoring system level resources, the memorystatus code is also responsible
61 1. Fill in the system health state by calling `memorystatus_health_check`)
63 1. Check if the system is healthy via `memorystatus_is_system_healthy`
64 …system is unhealthy, pick a recovery action and perform it. See `memorystatus_pick_action` (in `bs…
65 1. Go back to step 1 until the system is healthy and the thread can block.
69 thread is woken up *blindly* and it will do a full system health check.
73 The memorystatus subsystem has 210 priority levels. Every process in the system (except launchd) ha…
117 - `purgeable`: The number of purgeable volatile pages in the system. Purgeable memory is an API for…
119 …y pressure, this can generally be approximated to `free + file_backed` for a system under pressure.
130 \*Note that the memorystatus pressure threshold does *not* determine the "system memory pressure le…
145 This is the jetsam thread. It's responsible for running the system health check and performing most…
147 … blind and the thread will immediately do a health check to determine what's wrong with the system.
172 a snapshot of the system at the time that memorystatus performed
173 …system level memory statistics along with entries for each process in the system. Since we do not …
185 …system caches should be cleared before we do higher band jetsams. Userspace entities should do thi…