Searched refs:grow (Results 1 – 17 of 17) sorted by relevance
33 unsigned long grow; in expand_backing_store() local35 grow = PAGE_SIZE >> PAGE_SHIFT; in expand_backing_store()37 || (((vma->vm_mm->total_vm + grow) << PAGE_SHIFT) > current->rlim[RLIMIT_AS].rlim_cur)) in expand_backing_store()40 vma->vm_mm->total_vm += grow; in expand_backing_store()42 vma->vm_mm->locked_vm += grow; in expand_backing_store()
648 unsigned long grow; in expand_stack() local669 grow = (vma->vm_start - address) >> PAGE_SHIFT; in expand_stack()671 ((vma->vm_mm->total_vm + grow) << PAGE_SHIFT) > current->rlim[RLIMIT_AS].rlim_cur) { in expand_stack()677 … ((vma->vm_mm->locked_vm + grow) << PAGE_SHIFT) > current->rlim[RLIMIT_MEMLOCK].rlim_cur) { in expand_stack()684 vma->vm_pgoff -= grow; in expand_stack()685 vma->vm_mm->total_vm += grow; in expand_stack()687 vma->vm_mm->locked_vm += grow; in expand_stack()
17 read-write. The resize keyword with no value will grow
724 grow and shrink dynamically.
12 cdrom drive. It will grow as the questions arise. ;-)
116 cannot grow to much.
68 splitting," that allows "virtual packets" to grow as large as 64K each,
197 the readahead value to grow larger, resulting in more blocks339 bigger vm_balance is, the easier the active cache will grow,
221 static int nl_pid_hash_rehash(struct nl_pid_hash *hash, int grow) in nl_pid_hash_rehash() argument232 if (grow) { in nl_pid_hash_rehash()
93 PAGE_CACHE_SIZE may grow in future (if I interpret the comment
29 as the top of the userspace stack to allow the stack to grow as
280 beqs busy_fr |if unimp, grow to busy
136 ! It can be valid access, such as stack grow and/or C-O-W.
76 when the catalog or extents overflow files grow. that just leaves1897 Updated to use truncate() to grow full trees.
883 forks will cause the corresponding fork to grow (with zero padding) or
191 An example of how big /dev can grow is if we consider SCSI devices:
5996 If you say Y here, the kernel's internal ARP cache will never grow