Lines Matching full:with

10 or you can directly request pages from the page allocator with
18 Diversity of the allocation APIs combined with the numerous GFP flags
49     to provide a suitable fallback to cope with such failures where
83 with limited addressing capabilities. So unless you are writing a
84 driver for a device with such restrictions, avoid using these flags.
85 And even with hardware with restrictions it is preferable to use
108     non sleeping allocation with an expensive fallback so it can access
110     context with an expensive slow path fallback.
142 The maximal size of a chunk that can be allocated with `kmalloc` is
147 The address of a chunk allocated with `kmalloc` is aligned to at least
153 Chunks allocated with kmalloc() can be resized with krealloc(). Similarly
163 try to allocate memory with `kmalloc` and if the allocation fails it
164 will be retried with `vmalloc`. There are restrictions on which GFP
165 flags can be used with `kvmalloc`; please see kvmalloc_node() reference
170 cache allocator. The cache should be set up with kmem_cache_create() or
179 allocated by `kmem_cache_alloc` can be freed with `kmem_cache_free`, `kfree`
185 Memory allocated by `vmalloc` can be freed with `vfree` or `kvfree`.
186 Memory allocated by `kvmalloc` can be freed with `kvfree`.
187 Caches created by `kmem_cache_create` should be freed with