Lines Matching refs:we

13 The xnu memorystatus subsystem is responsible for recovering the system when we're running dangerou…
67 1. Log this state to the os log (or serial if we're early in boot)
69 …we sometimes do pre-emptive actions on a healthy system if we're somewhat low on a specific resour…
81 …otected by the `proc_list_mlock` (Yes this is bad for scalability. Ideally we'd use finer grain lo…
124 Since we purge purgeable memory and trim the secluded pool quickly under memory pressure, this can …
144 It's woken up via a call to `memorystatus_thread_wake` whenever any subsystem determines we're runn…
146 …_memorystatus_2`, and `VM_memorystatus_3`. But we currently only use `VM_memorystatus_1`. At one p…
170 …we do not want to wake up ReportCrash while the system is low on memory, we maintain one global sn…
172 …_get_jetsam_snapshot` in `bsd/kern/kern_memorystatus.c` for details. Since we only have one global…
176 …and uses it as an input for its freezer recommendation algorithm. However, we're not currently usi…
182 …we do higher band jetsams. Userspace entities should do this via purgeable memory if possible, or …