Home
last modified time | relevance | path

Searched refs:allocators (Results 1 – 21 of 21) sorted by relevance

/linux/Documentation/core-api/
H A Dgenalloc.rst10 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.
H A Ddma-api-howto.rst120 (i.e. __get_free_page*()) or the generic memory allocators
/linux/Documentation/filesystems/ext4/
H A Doverview.rst24 allocators
H A Dallocators.rst50 group, the allocators simply move on to the next block group. Allegedly
H A Datomic_writes.rst223 * :doc:`allocators` - Documentation on block allocation in ext4
/linux/drivers/md/dm-vdo/
H A Dslab-depot.c229 * check_summary_drain_complete() - Check whether an allocators summary has finished draining.
3838 * needed. The newly allocated slabs will not be distributed for use by the block allocators.
3867 &depot->allocators[depot->new_slab_count % depot->zone_count]; in allocate_slabs()
3904 return ((struct slab_depot *) context)->allocators[zone_number].thread_id; in get_allocator_thread_id()
3945 struct list_head *list = &depot->allocators[zone_number].dirty_slab_journals; in release_tail_block_locks()
4059 struct block_allocator *allocator = &depot->allocators[zone]; in initialize_block_allocator()
4198 /* Initialize the block allocators. */ in allocate_components()
4308 struct block_allocator *allocator = &depot->allocators[zone]; in vdo_free_slab_depot()
4501 /* The allocators are responsible for thread safety. */ in vdo_get_slab_depot_allocated_blocks()
4502 total += READ_ONCE(depot->allocators[zon in vdo_get_slab_depot_allocated_blocks()
[all...]
H A Dslab-depot.h28 * A slab_depot is responsible for managing all of the slabs and block allocators of a VDO. It has
511 /* The block allocators for this depot */
512 struct block_allocator allocators[]; member
H A Dphysical-zone.c343 zone->allocator = &vdo->depot->allocators[zone_number]; in initialize_zone()
/linux/drivers/media/test-drivers/vivid/
H A Dvivid-core.c167 static unsigned int allocators[VIVID_MAX_DEVS] = { [0 ... (VIVID_MAX_DEVS - 1)] = 0 }; variable
168 module_param_array(allocators, uint, NULL, 0444);
169 MODULE_PARM_DESC(allocators, " memory allocator selection, default is 0.\n"
921 if (allocators[dev->inst] != 1) in vivid_create_queue()
926 q->mem_ops = allocators[dev->inst] == 1 ? &vb2_dma_contig_memops : in vivid_create_queue()
1977 if (allocators[inst] == 1) in vivid_create_instance()
/linux/Documentation/gpu/nova/core/
H A Dfwsec.rst181 memory allocators need to wait for this scrubbing to complete).
/linux/Documentation/arch/sh/
H A Dnew-machine.rst154 - Consistent allocators (for boards that need special allocators,
/linux/Documentation/dev-tools/
H A Dkasan.rst78 For slab, both software KASAN modes support SLUB and SLAB allocators, while
476 in memory allocators), these accesses are valid.
H A Dkfence.rst309 The following describes the functions which are used by allocators as well as
/linux/drivers/media/platform/amphion/
H A Dvpu_v4l2.c473 struct device *allocators[]) in vpu_vb2_queue_setup() argument
/linux/Documentation/admin-guide/mm/
H A Dpagemap.rst124 the SLUB etc. memory allocators and various device drivers.
/linux/Documentation/mm/
H A Dhmm.rst18 related to using device specific memory allocators. In the second section, I
/linux/Documentation/driver-api/dmaengine/
H A Dprovider.rst111 structure. Any of the usual memory allocators will do, but you'll also
/linux/
H A DCREDITS1165 D: Slab allocators
2080 D: Slab allocators
2345 D: NUMA support, Slab allocators, Page migration
/linux/mm/
H A DKconfig136 read the description of each of the allocators below before
/linux/Documentation/process/
H A Dcoding-style.rst938 The kernel provides the following general purpose memory allocators:
/linux/Documentation/admin-guide/media/
H A Dvivid.rst288 - allocators: