Searched refs:behind (Results 1 – 4 of 4) sorted by relevance
592 { vm_object_offset_t behind = vm_default_behind * PAGE_SIZE_64; in vm_fault_deactivate_behind() local599 …if ((uint64_t)sequential_run >= behind && (sequential_run % (VM_DEFAULT_DEACTIVATE_BEHIND_CLUSTER … in vm_fault_deactivate_behind()606 if (offset >= behind) { in vm_fault_deactivate_behind()607 run_offset = 0 - behind; in vm_fault_deactivate_behind()612 if (offset < -behind) { in vm_fault_deactivate_behind()613 run_offset = behind; in vm_fault_deactivate_behind()
31 offers more information that can explain the rationale behind these
39 … higher buckets have used up enough CPU in the recent past such that its behind the lower buckets …
443 /* block behind the child starting up */