Searched refs:allocators (Results 1 – 20 of 20) sorted by relevance
| /linux/Documentation/core-api/ |
| A 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.
|
| A 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
|
| A D | dma-api-howto.rst | 120 (i.e. __get_free_page*()) or the generic memory allocators
|
| /linux/Documentation/filesystems/ext4/ |
| A D | overview.rst | 22 .. include:: allocators.rst
|
| A D | allocators.rst | 50 group, the allocators simply move on to the next block group. Allegedly
|
| /linux/drivers/md/dm-vdo/ |
| A D | slab-depot.c | 3800 &depot->allocators[depot->new_slab_count % depot->zone_count]; in allocate_slabs()
3992 struct block_allocator *allocator = &depot->allocators[zone]; in initialize_block_allocator()
4228 struct block_allocator *allocator = &depot->allocators[zone]; in vdo_free_slab_depot()
4421 total += READ_ONCE(depot->allocators[zone].allocated_blocks); in vdo_get_slab_depot_allocated_blocks()
4574 vdo_start_loading(&depot->allocators[zone_number].state, in load_allocator()
4606 struct block_allocator *allocator = &depot->allocators[zone_number]; in prepare_to_allocate()
4723 struct block_allocator *allocator = &depot->allocators[zone_number]; in register_new_slabs()
4830 vdo_start_draining(&depot->allocators[zone_number].state, in drain_allocator()
4922 vdo_start_resuming(&depot->allocators[zone_number].state, in resume_allocator()
4968 scrub_slabs(&depot->allocators[zone_number], NULL); in scrub_all_unrecovered_slabs()
[all …]
|
| A D | slab-depot.h | 501 struct block_allocator allocators[]; member
|
| A D | physical-zone.c | 343 zone->allocator = &vdo->depot->allocators[zone_number]; in initialize_zone()
|
| /linux/drivers/media/test-drivers/vivid/ |
| A D | vivid-core.c | 165 static unsigned int allocators[VIVID_MAX_DEVS] = { [0 ... (VIVID_MAX_DEVS - 1)] = 0 }; variable
166 module_param_array(allocators, uint, NULL, 0444);
167 MODULE_PARM_DESC(allocators, " memory allocator selection, default is 0.\n"
919 if (allocators[dev->inst] != 1) in vivid_create_queue()
924 q->mem_ops = allocators[dev->inst] == 1 ? &vb2_dma_contig_memops : in vivid_create_queue()
1975 if (allocators[inst] == 1) in vivid_create_instance()
|
| /linux/Documentation/arch/sh/ |
| A D | new-machine.rst | 154 - Consistent allocators (for boards that need special allocators,
|
| /linux/Documentation/admin-guide/mm/ |
| A D | pagemap.rst | 107 the SLUB etc. memory allocators and various device drivers.
|
| /linux/Documentation/dev-tools/ |
| A D | kasan.rst | 78 For slab, both software KASAN modes support SLUB and SLAB allocators, while
476 in memory allocators), these accesses are valid.
|
| A D | kfence.rst | 309 The following describes the functions which are used by allocators as well as
|
| /linux/drivers/media/platform/amphion/ |
| A D | vpu_v4l2.c | 473 struct device *allocators[]) in vpu_vb2_queue_setup() argument
|
| /linux/Documentation/mm/ |
| A D | hmm.rst | 18 related to using device specific memory allocators. In the second section, I
|
| /linux/Documentation/driver-api/dmaengine/ |
| A D | provider.rst | 111 structure. Any of the usual memory allocators will do, but you'll also
|
| /linux/mm/ |
| A D | Kconfig | 137 read the description of each of the allocators below before
|
| /linux/Documentation/process/ |
| A D | coding-style.rst | 935 The kernel provides the following general purpose memory allocators:
|
| /linux/Documentation/admin-guide/media/ |
| A D | vivid.rst | 288 - allocators:
|
| /linux/ |
| A D | CREDITS | 1145 D: Slab allocators
2301 D: NUMA support, Slab allocators, Page migration
|
Completed in 55 milliseconds