Searched refs:behind (Results 1 – 4 of 4) sorted by relevance
628 { vm_object_offset_t behind = vm_default_behind * PAGE_SIZE_64; in vm_fault_deactivate_behind() local635 …if ((uint64_t)sequential_run >= behind && (sequential_run % (VM_DEFAULT_DEACTIVATE_BEHIND_CLUSTER … in vm_fault_deactivate_behind()642 if (offset >= behind) { in vm_fault_deactivate_behind()643 run_offset = 0 - behind; in vm_fault_deactivate_behind()648 if (offset < -behind) { in vm_fault_deactivate_behind()649 run_offset = behind; in vm_fault_deactivate_behind()
32 to decode the message above, however sometimes it lags behind the introduction
41 …r buckets have used up enough CPU in the recent past such that they slip behind the lower buckets …
616 /* block behind the child starting up */