Lines Matching full:allocation

38 	use "local allocation" described below.  However, during boot
82 	A VMA policy will govern the allocation of pages that back
138 	support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
140 	Although hugetlbfs segments now support lazy allocation, their support
197 	closest to the node where the allocation takes place.
200 	This mode specifies that the allocation should be attempted
202 	allocation fails, the kernel will search other nodes, in order
209 	and the policy is interpreted as local allocation.  "Local"
210 	allocation policy can be viewed as a Preferred policy that
211 	starts at the node containing the cpu where the allocation
214 	It is possible for the user to specify that local allocation
226 	For allocation of anonymous pages and shared memory pages,
233 	local allocation.  That is, allocation will follow the per
236 	For allocation of page cache pages, Interleave mode indexes
247 	This mode specifies that the allocation should be preferably
249 	a memory pressure on all nodes in the nodemask, the allocation
282 	(local allocation).
333 	(local allocation).
359    or node lists, if any, for page allocation.  This is considered a "hot
361    allocation process, which may sleep during page reclamation, because the
378 3) Page allocation usage of task or vma policy occurs in the fault path where
381    freed out from under us while we're using it for page allocation.
390    extra reference on shared policies in the same query/allocation paths
397    more expensive to use in the page allocation path.  This is especially
470 closest to which page allocation will come from. Specifying the home node override
471 the default allocation policy to allocate memory close to the local node for an
514 memory sets are disjoint, "local" allocation is the only valid policy.