Searched refs:allocators (Results 1 – 18 of 18) sorted by relevance
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | genalloc.rst | 10 tested allocators. Back in 2005, Jes Sorensen lifted one of those
11 allocators from the sym53c8xx_2 driver and posted_ it as a generic module
12 for the creation of ad hoc memory allocators. This code was merged
123 writing of special-purpose memory allocators in the future.
|
| D | memory-allocation.rst | 11 `alloc_pages`. It is also possible to use more specialized allocators,
32 The GFP flags control the allocators behavior. They tell what memory
|
| D | dma-api-howto.rst | 120 (i.e. __get_free_page*()) or the generic memory allocators
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ext4/ |
| D | overview.rst | 22 .. include:: allocators.rst
|
| D | allocators.rst | 50 group, the allocators simply move on to the next block group. Allegedly
|
| /kernel/linux/linux-5.10/drivers/media/test-drivers/vivid/ |
| D | vivid-core.c | 166 static unsigned int allocators[VIVID_MAX_DEVS] = { [0 ... (VIVID_MAX_DEVS - 1)] = 0 }; variable
167 module_param_array(allocators, uint, NULL, 0444);
168 MODULE_PARM_DESC(allocators, " memory allocator selection, default is 0.\n"
840 if (allocators[dev->inst] != 1) in vivid_create_queue()
845 q->mem_ops = allocators[dev->inst] == 1 ? &vb2_dma_contig_memops : in vivid_create_queue()
1864 if (allocators[inst] == 1) in vivid_create_instance()
|
| /kernel/linux/linux-5.10/Documentation/sh/ |
| D | new-machine.rst | 154 - Consistent allocators (for boards that need special allocators,
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | pagemap.rst | 107 the SLUB etc. memory allocators and various device drivers.
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kasan.rst | 38 Both KASAN modes work with both SLUB and SLAB memory allocators.
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | hmm.rst | 20 related to using device specific memory allocators. In the second section, I
|
| /kernel/linux/linux-5.10/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 111 structure. Any of the usual memory allocators will do, but you'll also
|
| /kernel/linux/linux-5.10/mm/ |
| D | Kconfig | 692 read the description of each of the allocators below before
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | coding-style.rst | 868 The kernel provides the following general purpose memory allocators:
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | vivid.rst | 288 - allocators:
|
| /kernel/linux/linux-5.10/ |
| D | CREDITS | 1083 D: Slab allocators
2169 D: NUMA support, Slab allocators, Page migration
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/ |
| D | 0038_linux_drivers_mxc.patch | 141711 + gcmkONERROR(gckDEBUGFS_DIR_Init(dir, device->debugfsDir.root, "allocators"));
153028 + /* Walk all allocators. */
154827 + /* Walk all allocators. */
159147 + /* Walk all allocators. */
193587 + struct device *allocators[])
201748 + struct device *allocators[])
|
| D | 0036_linux_drivers_staging.patch | 18514 +/* Everything else is the common backend to all the allocators */
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/ |
| D | 0005_linux_include.patch | 8749 + * both the FQID and BPID allocators. The fsl_usdpaa driver also uses this
|