Home
last modified time | relevance | path

Searched refs:GFP (Results 1 – 13 of 13) sorted by relevance

/linux/Documentation/translations/zh_CN/core-api/
H A Dmemory-allocation.rst24 大多数的内存分配API使用GFP标志来表达该内存应该如何分配。GFP的缩写代表
27 （内存）分配API的多样性与众多的GFP标志相结合，使得“我应该如何分配内存？”这个问
34 当然，有些情况下必须使用其他分配API和不同的GFP标志。
38 GFP标志控制分配器的行为。它们告诉我们哪些内存区域可以被使用，分配器应该多努力寻
39 找空闲的内存，这些内存是否可以被用户空间访问等等。内存管理API为GFP标志和它们的
72 其他传统的GFP标志是 ``GFP_DMA`` 和 ``GFP_DMA32`` 。它们用于确保分配的内存可以被寻
76 GFP标志和回收行为
127 试用kmalloc分配内存，如果分配失败，将用 `vmalloc` 重新尝试。对于哪些GFP标志可以与 `kvmalloc`
H A Dgfp_mask-from-fs-io.rst16 从FS/IO上下文中使用的GFP掩码
H A Dxarray.rst136 防XArray需要分配内存来存储这个条目。如果该条目被删除，则不需要进行内存分配，指定的GFP标志将被忽
139 没有内存可供分配是可能的，特别是如果你传递了一组限制性的GFP标志。在这种情况下，这些函数会返回一
H A Didr.rst62 如果在从IDR分配一个新ID时需要带锁，您可能需要传递一组限制性的GFP标志，但这可能导
/linux/drivers/gpu/drm/i915/gem/selftests/
H A Dhuge_gem_object.c30 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_RETRY_MAYFAIL) in huge_get_pages() macro
41 pages = kmalloc(sizeof(*pages), GFP); in huge_get_pages()
45 if (sg_alloc_table(pages, npages, GFP)) { in huge_get_pages()
54 page = alloc_page(GFP | __GFP_HIGHMEM); in huge_get_pages()
82 #undef GFP in huge_get_pages()
H A Dhuge_pages.c80 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY) in get_huge_pages() macro
91 st = kmalloc(sizeof(*st), GFP); in get_huge_pages()
95 if (sg_alloc_table(st, obj->base.size >> PAGE_SHIFT, GFP)) { in get_huge_pages()
119 page = alloc_pages(GFP | __GFP_ZERO, order); in get_huge_pages()
223 st = kmalloc(sizeof(*st), GFP); in fake_get_huge_pages()
227 if (sg_alloc_table(st, obj->base.size >> PAGE_SHIFT, GFP)) { in fake_get_huge_pages()
273 st = kmalloc(sizeof(*st), GFP); in fake_get_huge_pages_single()
277 if (sg_alloc_table(st, 1, GFP)) { in fake_get_huge_pages_single()
296 #undef GFP in fake_get_huge_pages_single()
/linux/security/apparmor/include/
H A Dlib.h225 * @GFP: memory allocation type to use
234 #define fn_label_build(L, P, GFP, FN) \
245 if (vec_setup(label, __lvec, (L)->size, (GFP))) { \
259 if (!vec_setup(profile, __pvec, __count, (GFP))) { \
267 __count, (GFP)); \
299 #define fn_label_build_in_ns(L, P, GFP, NS_FN, OTHER_FN) \
301 fn_label_build((L), (P), (GFP), \
235 fn_label_build(L,P,GFP,FN) global() argument
300 fn_label_build_in_ns(L,P,GFP,NS_FN,OTHER_FN) global() argument
H A Dlabel.h28 #define vec_setup(T, V, N, GFP) \ argument
36 (V) = kzalloc(sizeof(struct aa_ ## T *) * (N), (GFP)); \
/linux/Documentation/core-api/
H A Dmemory-allocation.rst14 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
81 Other legacy GFP flags are ``GFP_DMA`` and ``GFP_DMA32``. They are
88 GFP flags and reclaim behavior
164 will be retried with `vmalloc`. There are restrictions on which GFP
H A Dmm-api.rst32 :doc: Useful GFP flag combinations
H A Didr.rst64 you may need to pass a restrictive set of GFP flags, which can lead
H A Dxarray.rst175 and the GFP flags specified will be ignored.
178 a restrictive set of GFP flags. In that case, the functions return a
/linux/drivers/gpu/drm/i915/selftests/
H A Di915_gem_gtt.c60 #define GFP (GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY) in fake_get_pages() macro
66 pages = kmalloc(sizeof(*pages), GFP); in fake_get_pages()
77 if (sg_alloc_table(pages, rem, GFP)) { in fake_get_pages()
98 #undef GFP in fake_get_pages()