Home
last modified time | relevance | path

Searched refs:vmalloc (Results 1 – 25 of 277) sorted by relevance

12345678910>>...12

/linux/lib/
H A Dtest_vmalloc.c4 * Test module for stress and analyze performance of vmalloc allocator.
10 #include <linux/vmalloc.h>
158 p = vmalloc(n * PAGE_SIZE); in random_size_alloc_test()
177 ptr = vmalloc(sizeof(void *) * 15000); in long_busy_list_alloc_test()
182 ptr[i] = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test()
185 ptr_1 = vmalloc(100 * PAGE_SIZE); in long_busy_list_alloc_test()
189 ptr_2 = vmalloc(1 * PAGE_SIZE); in long_busy_list_alloc_test()
223 ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test()
227 junk_ptr = vmalloc(sizeof(void *) * junk_length); in full_fit_alloc_test()
234 ptr[i] = vmalloc( in full_fit_alloc_test()
[all...]
H A Ddecompress_unxz.c162 #undef vmalloc
166 #define vmalloc(size) malloc(size) macro
/linux/Documentation/translations/zh_TW/dev-tools/
H A Dkasan.rst64 通用KASAN支持在所有的slab、page_alloc、vmap、vmalloc、堆棧和全局內存
132 - ``kasan.vmalloc=off`` or ``=on`` 禁用或啓用vmalloc分配的標記（默認： ``on`` ）。
/linux/Documentation/translations/zh_CN/core-api/
H A Dmemory-allocation.rst20 系列分配小块内存，使用 `vmalloc` 及其派生产品分配大的几乎连续的区域，或者
127 试用kmalloc分配内存，如果分配失败，将用 `vmalloc` 重新尝试。对于哪些GFP标志可以与 `kvmalloc`
136 当分配的内存不再需要时，它必须被释放。你可以使用kvfree()来处理用 `kmalloc` 、 `vmalloc`
H A Dgfp_mask-from-fs-io.rst61 复这些分配是相当不容易的。这意味着用GFP_NOFS/GFP_NOIO调用 ``vmalloc`` 几乎
64 在理想的世界中，上层应该已经标记了危险的上下文，因此不需要特别的照顾， ``vmalloc``
/linux/scripts/coccinelle/api/
H A Dkfree_mismatch.cocci4 /// vmalloc'ed by vfree functions and kvmalloc'ed by kvfree
31 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|
44 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|
71 ... when != if (...) { ... E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|vmalloc_exec\|vmalloc_32\|vmalloc_32_user\|__vmalloc\|__vmalloc_node_range\|__vmalloc_node\)(...); ... }
85 ... when != if (...) { ... E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|vmalloc_exec\|vmalloc_32\|vmalloc_32_user\|__vmalloc\|__vmalloc_node_range\|__vmalloc_node\)(...); ... }
97 * E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|
110 E = \(vmalloc\|vzalloc\|vmalloc_user\|vmalloc_node\|vzalloc_node\|
185 msg = "WARNING vmalloc is used to allocate this memory at line %s" % (a[0].line)
193 msg = "WARNING vmalloc is used to allocate this memory at line %s" % (a[0].line)
218 msg = "WARNING kmalloc (line %s) && vmalloc (lin
[all...]
H A Dkvmalloc.cocci3 /// Find if/else condition with kmalloc/vmalloc calls.
41 * E = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...)
53 * E = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...)
65 * x = \(vmalloc\|vzalloc\|vmalloc_node\|vzalloc_node\)(..., size, ...)
97 - E = vmalloc(size);
103 - E = vmalloc(size);
108 - E = vmalloc(size);
113 - E = vmalloc(size);
118 - x = vmalloc(size);
123 - x = vmalloc(siz
[all...]
/linux/Documentation/core-api/
H A Dgfp_mask-from-fs-io.rst58 Since v5.17, and specifically after the commit 451769ebb7e79 ("mm/vmalloc:
59 alloc GFP_NO{FS,IO} for vmalloc"), GFP_NOFS/GFP_NOIO are now supported in
60 ``[k]vmalloc`` by implicitly using scope API.
62 In earlier kernels ``vmalloc`` didn't support GFP_NOFS semantic because there
64 that calling ``vmalloc`` with GFP_NOFS/GFP_NOIO was almost always a bug.
67 and so no special care is required and ``vmalloc`` should be called without any
70 wrap ``vmalloc`` by the scope API with a comment explaining the problem.
/linux/scripts/coccinelle/api/alloc/
H A Dalloc_cast.cocci35 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\|
58 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\|
81 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\|
98 kmem_cache_alloc_node\|kmalloc_node\|kzalloc_node\|vmalloc\|vzalloc\|
H A Dzalloc-simple.cocci37 * x = (T)\(kmalloc(E1, ...)\|vmalloc(E1)\|dma_alloc_coherent(...,E1,...)\|
64 - x = vmalloc(E1);
67 - x = (T *)vmalloc(E1);
70 - x = (T)vmalloc(E1);
182 x = (T)vmalloc@p(E1);
200 msg="WARNING: vzalloc should be used for %s, instead of vmalloc/memset" % (x)
/linux/fs/jffs2/
H A Dcompr_lzo.c15 #include <linux/vmalloc.h>
32 lzo_mem = vmalloc(LZO1X_MEM_COMPRESS); in alloc_workspace()
33 lzo_compress_buf = vmalloc(lzo1x_worst_compress(PAGE_SIZE)); in alloc_workspace()
H A Dcompr_zlib.c39 #include <linux/vmalloc.h>
45 def_strm.workspace = vmalloc(zlib_deflate_workspacesize(MAX_WBITS, in alloc_workspaces()
52 inf_strm.workspace = vmalloc(zlib_inflate_workspacesize()); in alloc_workspaces()
/linux/Documentation/translations/zh_CN/mm/
H A Dvmalloced-kernel-stacks.rst
/linux/Documentation/translations/zh_CN/dev-tools/
H A Dkmsan.rst373 2. 对于 vmalloc 内存和模块，内存范围、影子和源之间有一个直接映射。KMSAN 将
374 vmalloc 区域缩小了 3/4，仅使前四分之一可用于 ``vmalloc()``。vmalloc
H A Dkmemleak.rst83 通过 :c:func:`kmalloc`, :c:func:`vmalloc`, :c:func:`kmem_cache_alloc` 以及同类
141 - ``kmemleak_vmalloc`` - 通知一个使用 vmalloc() 的内存分配
/linux/sound/drivers/opl4/
H A Dopl4_proc.c8 #include <linux/vmalloc.h>
46 buf = vmalloc(count); in snd_opl4_mem_proc_read()
67 buf = vmalloc(count); in snd_opl4_mem_proc_write()
/linux/fs/squashfs/
H A Dlzo_wrapper.c14 #include <linux/vmalloc.h>
35 stream->input = vmalloc(block_size); in lzo_init()
38 stream->output = vmalloc(block_size); in lzo_init()
H A Dlz4_wrapper.c10 #include <linux/vmalloc.h>
60 stream->input = vmalloc(block_size); in lz4_init()
63 stream->output = vmalloc(block_size); in lz4_init()
/linux/Documentation/translations/zh_CN/arch/riscv/
H A Dvm-layout.rst58 ffffffc800000000 | -224 GB | ffffffd7ffffffff | 64 GB | vmalloc/ioremap space
94 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
/linux/Documentation/arch/arm/
H A Dporting.rst97 Virtual addresses bounding the vmalloc() area. There must not be
98 any static mappings in this area; vmalloc will overwrite them.
100 Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the
105 between virtual RAM and the vmalloc area. We do this to allow
H A Dmemory.rst57 mapping within the vmalloc space.
59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
60 Memory returned by vmalloc/ioremap will
/linux/Documentation/arch/s390/
H A Dmm.rst87 +- VMALLOC_START --+ vmalloc area start
89 | vmalloc area | KASAN shallowly populated in case
/linux/Documentation/arch/riscv/
H A Dvm-layout.rst53 ffffffc600000000 | -232 GB | ffffffd5ffffffff | 64 GB | vmalloc/ioremap space
90 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
126 ff20000000000000 | -56 PB | ff5fffffffffffff | 16 PB | vmalloc/ioremap space
/linux/drivers/video/
H A Dvgastate.c19 #include <linux/vmalloc.h>
362 saved->vga_cmap = vmalloc(768); in save_vga()
384 saved->attr = vmalloc(total); in save_vga()
421 saved->vga_font0 = vmalloc(4 * 8192); in save_vga()
433 saved->vga_font1 = vmalloc(state->memsize); in save_vga()
444 saved->vga_text = vmalloc(8192 * 2); in save_vga()
/linux/drivers/mtd/tests/
H A Dstresstest.c19 #include <linux/vmalloc.h>
179 readbuf = vmalloc(bufsize); in mtd_stresstest_init()
180 writebuf = vmalloc(bufsize); in mtd_stresstest_init()

12345678910>>...12