Lines Matching full:allocation

14  * typedef gfp_t - Memory allocation flags.
18  * the underlying memory allocation function.  Not every GFP flag is
96  * pages being in one zone (fair zone allocation policy).
98  * %__GFP_HARDWALL enforces the cpuset memory allocation policy.
100  * %__GFP_THISNODE forces the allocation to be satisfied from the requested
103  * %__GFP_ACCOUNT causes the allocation to be accounted to kmemcg.
126  * the caller guarantees the allocation will allow more memory to be freed
165  * canonical example is THP allocation where a fallback is cheap but
200  * If the allocation does fail, and the caller is in a position to
205  * cannot handle allocation failures. The allocation could block
229  * %__GFP_NOWARN suppresses allocation failure reports.
265  * %GFP_ATOMIC users can not sleep and need the allocation to succeed. A lower
273  * %GFP_KERNEL_ACCOUNT is the same as GFP_KERNEL, except the allocation is
283  * perform any IO with a short explanation why. All allocation requests
289  * recurse into the FS layer with a short explanation why. All allocation
309  * move once in use. An example may be a hardware allocation that maps
367  * Test whether @gfp_flags indicates that the allocation is from the
370  * An allocation being allowed to block doesn't mean it owns the %current
372  * allocation context is nested inside whatever %current was doing at the
373  * time of the original allocation.  The nested allocation may be allowed
377  * %true result from this function indicates that the allocation context
411  * But GFP_MOVABLE is not only a zone specifier but also an allocation
652  * hibernation, it is used by PM to avoid I/O during memory allocation while