Searched refs:behind (Results 1 – 5 of 5) sorted by relevance
666 { vm_object_offset_t behind = vm_default_behind * PAGE_SIZE_64; in vm_fault_deactivate_behind() local673 …if ((uint64_t)sequential_run >= behind && (sequential_run % (VM_DEFAULT_DEACTIVATE_BEHIND_CLUSTER … in vm_fault_deactivate_behind()680 if (offset >= behind) { in vm_fault_deactivate_behind()681 run_offset = 0 - behind; in vm_fault_deactivate_behind()686 if (offset < -behind) { in vm_fault_deactivate_behind()687 run_offset = behind; in vm_fault_deactivate_behind()
109 quarantine is cleared. The idea behind this policy is that maintaining a good
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 …
617 /* block behind the child starting up */