Searched refs:GFP (Results 1 – 11 of 11) sorted by relevance
| /Linux-v5.4/drivers/gpu/drm/i915/gem/selftests/ |
| D | huge_gem_object.c | 26 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY) in huge_get_pages() macro
33 pages = kmalloc(sizeof(*pages), GFP); in huge_get_pages()
37 if (sg_alloc_table(pages, npages, GFP)) { in huge_get_pages()
46 page = alloc_page(GFP | __GFP_HIGHMEM); in huge_get_pages()
75 #undef GFP in huge_get_pages()
|
| D | huge_pages.c | 58 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY) in get_huge_pages() macro
65 st = kmalloc(sizeof(*st), GFP); in get_huge_pages()
69 if (sg_alloc_table(st, obj->base.size >> PAGE_SHIFT, GFP)) { in get_huge_pages()
93 page = alloc_pages(GFP | __GFP_ZERO, order); in get_huge_pages()
189 st = kmalloc(sizeof(*st), GFP); in fake_get_huge_pages()
193 if (sg_alloc_table(st, obj->base.size >> PAGE_SHIFT, GFP)) { in fake_get_huge_pages()
244 st = kmalloc(sizeof(*st), GFP); in fake_get_huge_pages_single()
248 if (sg_alloc_table(st, 1, GFP)) { in fake_get_huge_pages_single()
269 #undef GFP in fake_get_huge_pages_single()
|
| /Linux-v5.4/security/apparmor/include/ |
| D | lib.h | 217 #define fn_label_build(L, P, GFP, FN) \ argument
228 if (vec_setup(label, __lvec, (L)->size, (GFP))) { \
242 if (!vec_setup(profile, __pvec, __count, (GFP))) { \
250 __count, (GFP)); \
282 #define fn_label_build_in_ns(L, P, GFP, NS_FN, OTHER_FN) \ argument
284 fn_label_build((L), (P), (GFP), \
|
| D | label.h | 28 #define vec_setup(T, V, N, GFP) \ argument
36 (V) = kzalloc(sizeof(struct aa_ ## T *) * (N), (GFP)); \
|
| /Linux-v5.4/Documentation/core-api/ |
| D | mm-api.rst | 22 Functions which need to allocate memory often use GFP flags to express
23 how that memory should be allocated. The GFP acronym stands for "get
24 free pages", the underlying memory allocation function. Not every GFP
38 :doc: Useful GFP flag combinations
|
| D | memory-allocation.rst | 14 Most of the memory allocation APIs use GFP flags to express how that
15 memory should be allocated. The GFP acronym stands for "get free
18 Diversity of the allocation APIs combined with the numerous GFP flags
26 Of course there are cases when other allocation APIs and different GFP
32 The GFP flags control the allocators behavior. They tell what memory
36 reference documentation for the GFP flags and their combinations and
80 Other legacy GFP flags are ``GFP_DMA`` and ``GFP_DMA32``. They are
114 restrictions on which GFP flags can be used with `kvmalloc`; please
|
| D | gfp_mask-from-fs-io.rst | 4 GFP masks used from FS/IO context
|
| D | idr.rst | 61 you may need to pass a restrictive set of GFP flags, which can lead
|
| D | xarray.rst | 162 and the GFP flags specified will be ignored.
165 a restrictive set of GFP flags. In that case, the functions return a
|
| /Linux-v5.4/drivers/gpu/drm/i915/selftests/ |
| D | i915_gem_gtt.c | 59 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY) in fake_get_pages() macro
66 pages = kmalloc(sizeof(*pages), GFP); in fake_get_pages()
71 if (sg_alloc_table(pages, rem, GFP)) { in fake_get_pages()
96 #undef GFP in fake_get_pages()
|
| /Linux-v5.4/Documentation/block/ |
| D | biodoc.rst | 215 GFP flags) when allocating bounce buffers, to avoid certain highmem
|
