Lines Matching full:allocation

80  * pages being in one zone (fair zone allocation policy).
82 * %__GFP_HARDWALL enforces the cpuset memory allocation policy.
84 * %__GFP_THISNODE forces the allocation to be satisfied from the requested
87 * %__GFP_ACCOUNT causes the allocation to be accounted to kmemcg.
110 * the caller guarantees the allocation will allow more memory to be freed
149 * canonical example is THP allocation where a fallback is cheap but
184 * If the allocation does fail, and the caller is in a position to
189 * cannot handle allocation failures. The allocation could block
213 * %__GFP_NOWARN suppresses allocation failure reports.
240 * %GFP_ATOMIC users can not sleep and need the allocation to succeed. A lower
248 * %GFP_KERNEL_ACCOUNT is the same as GFP_KERNEL, except the allocation is
258 * perform any IO with a short explanation why. All allocation requests
264 * recurse into the FS layer with a short explanation why. All allocation
284 * move once in use. An example may be a hardware allocation that maps
341 * Test whether @gfp_flags indicates that the allocation is from the
344 * An allocation being allowed to block doesn't mean it owns the %current
346 * allocation context is nested inside whatever %current was doing at the
347 * time of the original allocation. The nested allocation may be allowed
351 * %true result from this function indicates that the allocation context
385 * But GFP_MOVABLE is not only a zone specifier but also an allocation
606 * hibernation, it is used by PM to avoid I/O during memory allocation while