Lines Matching full:allocate

17  * UDS and VDO keep track of which threads are allowed to allocate memory freely, and which threads
35  * If no flag is supplied, the thread is always allowed to allocate storage without complaint.
63  * We do not use kernel functions like the kvasprintf() method, which allocate memory indirectly
70  * We allocate very few large objects, and allocation/deallocation isn't done in a
159  * vmalloc can allocate any integral number of pages.
161  * kmalloc can allocate any number of bytes up to a configured limit, which defaults to 8 megabytes
169  * The advantages of kmalloc do not help out UDS or VDO, because we allocate all our memory up
181  * @size: How many bytes to allocate
189  * Allocate storage based on memory size and alignment, logging an error if the allocation fails.
235 			 * It is possible for kmalloc to fail to allocate memory because there is  in vdo_allocate_memory()
250 			 * It is possible for __vmalloc to fail to allocate memory because there  in vdo_allocate_memory()
287 		vdo_log_error("Could not allocate %zu bytes for %s in %u msecs",  in vdo_allocate_memory()
297  * Allocate storage based on memory size, failing immediately if the required memory is not
334  * @size: The new size to allocate