Searched refs:ahead (Results 1 – 5 of 5) sorted by relevance
155 int ahead);1161 int ahead, behind, cluster_offset, rv; in vm_fault_getpages() local1198 ahead = 0; in vm_fault_getpages()1203 ahead = nera; in vm_fault_getpages()1218 ahead = VM_FAULT_READ_DEFAULT - 1 - cluster_offset; in vm_fault_getpages()1220 ahead = ulmin(ahead, atop(e_end - fs->vaddr) - 1); in vm_fault_getpages()1223 *aheadp = ahead; in vm_fault_getpages()1281 int ahead, behind, faultcount; in vm_fault() local1479 faultcount = behind + 1 + ahead; in vm_fault()1591 faultcount > 0 ? ahead : PFFOR, false); in vm_fault()[all …]
237 int ahead; in default_phys_pager_populate() local251 ahead = MIN(end - i, PHYSALLOC); in default_phys_pager_populate()253 VM_ALLOC_NORMAL | VM_ALLOC_COUNT(ahead)); in default_phys_pager_populate()
75 maintainers after a few weeks, go ahead and take it.
84 related physical number is also put ahead of those names which helps cross
2069 Clarify that clientsCronTrackExpansiveClients() indexes may jump ahead.