Lines Matching full:be

15 memory should be allocated. The GFP acronym stands for "get free
27 flags must be used.
33 zones can be used, how hard the allocator should try to find free
34 memory, whether the memory can be accessed by the userspace etc. The
43     direct reclaim may be triggered under memory pressure; the calling
44     context must be allowed to sleep.
49     have a reasonable fallback should be using ``GFP_NOWARN``.
51     will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
52   * Untrusted allocations triggered from userspace should be a subject
55     allocations that should be accounted.
61     will be directly accessible by the kernel and implies that the
65     but it is not required to be directly accessible by the kernel. An
66     example may be a hardware allocation that maps data directly into
70     must be directly accessible by the kernel.
91 from the :c:func:`kmalloc` family. And, to be on the safe size it's
96 The maximal size of a chunk that can be allocated with `kmalloc` is
103 alignment is also guaranteed to be at least the respective size.
113 allocation fails it will be retried with `vmalloc`. There are
114 restrictions on which GFP flags can be used with `kvmalloc`; please
119 cache allocator. The cache should be set up with
121 before it can be used. The second function should be used if a part of
122 the cache might be copied to the userspace.  After the cache is
126 When the allocated memory is no longer needed it must be freed. You
128 `vmalloc` and `kvmalloc`. The slab caches should be freed with