Lines Matching refs:we

17 …nerally speaking, we want the freezer to run when the device is under some memory pressure but bef…
23we call `task_freeze` (`osfmk/kern/task.c`) which calls `vm_map_freeze` (`osfmk/vm/vm_map.c`). `vm…
25we have finished creating this contiguous compressor VA range, we put those segments on the swapou…
32 …y that's simply mapped into the same process in multiple places though, so we do a quick forward s…
42we can get rid of these limits. However, when we tried to remove them we discovered they were mask…
47 …tly, we freeze processes in the idle band in LRU order (apps that have been idle the longest get f…
52 …reeze the leader process first (we skip coalition members that are not the leader). Once we freeze…
66 When a frozen process is resumed we call it a thaw. Functionally, this is identical to a regular ap…
72we may re-freeze it. The exact heuristics for re-freeze are determined by the freezer thread. See …
84we have a limited number of slots in the freezer (and a swap file limit), so we don't have to keep…
91 …rystatus_freeze.c`). This interval tracks the number of writes and ensures we stay under the budge…
93 …et_budget` in `bsd/vm/vm_compressor_backing_file.c` for details. Note that we call this every day,…
100 …e not been unified. This policy should be re-visited before determining if we can go back to using…
112 …rocesses\_max | The max. number of processes that can be frozen. Note that we can go a bit above t…
118 | kern.memorystatus\_freezer\_use\_ordered\_list | Should we use the ordered app list? See [app sel…
119 | kern.memorystatus\_freezer\_use\_demotion\_list | Should we use the ordered demotion list? |