Lines Matching full:allocation

40 	use "local allocation" described below.  However, during boot
84 	A VMA policy will govern the allocation of pages that back
140 	support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
142 	Although hugetlbfs segments now support lazy allocation, their support
199 	closest to the node where the allocation takes place.
202 	This mode specifies that the allocation should be attempted
204 	allocation fails, the kernel will search other nodes, in order
211 	and the policy is interpreted as local allocation.  "Local"
212 	allocation policy can be viewed as a Preferred policy that
213 	starts at the node containing the cpu where the allocation
216 	It is possible for the user to specify that local allocation
228 	For allocation of anonymous pages and shared memory pages,
235 	local allocation.  That is, allocation will follow the per
238 	For allocation of page cache pages, Interleave mode indexes
249 	This mode specifices that the allocation should be preferrably
251 	a memory pressure on all nodes in the nodemask, the allocation
284 	(local allocation).
335 	(local allocation).
361    or node lists, if any, for page allocation.  This is considered a "hot
363    allocation process, which may sleep during page reclaimation, because the
380 3) Page allocation usage of task or vma policy occurs in the fault path where
383    freed out from under us while we're using it for page allocation.
392    extra reference on shared policies in the same query/allocation paths
399    more expensive to use in the page allocation path.  This is especially
472 closest to which page allocation will come from. Specifying the home node override
473 the default allocation policy to allocate memory close to the local node for an
516 memory sets are disjoint, "local" allocation is the only valid policy.