Home
last modified time | relevance | path

Searched full:areas (Results 1 – 25 of 364) sorted by relevance

12345678910>>...15

/linux/Documentation/userspace-api/media/v4l/
H A Dmetafmt-vsp1-hgt.rst26 between 1 and 16 depending on the Hue areas configuration. Finding the
35 how the HGT Hue areas are configured. There are 6 user configurable Hue
36 Areas which can be configured to cover overlapping Hue values:
59 When two consecutive areas don't overlap (n+1L is equal to nU) the boundary
64 with a hue value included in the overlapping region between two areas (between
65 n+1L and nU excluded) are attributed to both areas and given a weight for each
66 of these areas proportional to their position along the diagonal lines
/linux/kernel/dma/
H A Dswiotlb.c124 * otherwise a segment may span two or more areas. It conflicts with free
144 * swiotlb_adjust_nareas() - adjust the number of areas and slots
145 * @nareas: Desired number of areas. Zero is treated as 1.
147 * Adjust the default number of areas in a memory pool.
167 * limit_nareas() - get the maximum number of areas for a given memory pool size
168 * @nareas: Desired number of areas.
171 * Limit the number of areas to the maximum possible number of areas in
174 * Return: Maximum possible number of areas.
338 pool->areas[i].index = 0; in swiotlb_mark_pool_used()
339 pool->areas[i].used = pool->area_nslabs; in swiotlb_mark_pool_used()
[all …]
/linux/Documentation/core-api/
H A Dswiotlb.rst165 Slots are also grouped into "areas", with the constraint that a slot set exists
167 manipulate the slots in that area. The division into areas avoids contending
169 VM. The number of areas defaults to the number of CPUs in the system for
172 number of areas can also be set via the "swiotlb=" kernel boot parameter.
175 does not have enough free space, areas associated with other CPUs are tried
178 overall. But an allocation request does not fail unless all areas do not have
181 IO_TLB_SIZE, IO_TLB_SEGSIZE, and the number of areas must all be powers of 2 as
183 number of areas is rounded up to a power of 2 if necessary to meet this
220 The number of areas in a dynamic pool may be different from the number of areas
222 the number of areas will likely be smaller. For example, with a new pool size
[all …]
/linux/Documentation/admin-guide/mm/
H A Dksm.rst17 The KSM daemon ksmd periodically scans those areas of user memory
33 KSM only operates on those areas of address space which an application
62 Like other madvise calls, they are intended for use on mapped areas of
64 includes unmapped gaps (though working on the intervening mapped areas),
68 restricting its use to areas likely to benefit. KSM's scans may use a lot
115 leave mergeable areas registered for next run.
210 how many times all mergeable areas have been scanned
H A Dconcepts.rst146 call. Usually, the anonymous mappings only define virtual memory areas
199 necessary to allocate large physically contiguous memory areas. Such
206 physically contiguous areas become possible.
/linux/include/trace/events/
H A Dvmalloc.h54 * purge_vmap_area_lazy - called when vmap areas were lazily freed
57 * @npurged: numbed of purged vmap areas
94 * outstanding areas and a maximum allowed threshold before
/linux/include/linux/
H A Dswiotlb.h65 * @nareas: Number of areas in the pool.
67 * @areas: Array of memory area descriptors.
82 struct io_tlb_area *areas; member
107 * across all areas. Used only for calculating used_hiwater via boot
112 * are currently used across all areas.
/linux/Documentation/ABI/testing/
H A Dsysfs-devices-platform-docg37 keylocked. Each docg3 chip (or floor) has 2 protection areas,
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
/linux/arch/powerpc/platforms/pseries/
H A Dkexec.c26 * kernel steps on the old memory allocated to these areas before the in pseries_kexec_cpu_down()
27 * new kexec-kernel happens to allocate and register new areas, in pseries_kexec_cpu_down()
/linux/Documentation/security/
H A Dself-protection.rst35 areas of the kernel that can be used to redirect execution. This ranges
37 APIs hard to use incorrectly, minimizing the areas of writable kernel
50 Any areas of the kernel with executable memory must not be writable.
73 Vast areas of kernel memory contain function pointers that are looked
177 other memory areas.
251 initializations. If the base address of these areas is not the same
/linux/arch/sh/boards/mach-sdk7786/
H A Dfpga.c17 * The FPGA can be mapped in any of the generally available areas,
30 * Iterate over all of the areas where the FPGA could be mapped. in sdk7786_fpga_probe()
/linux/io_uring/
H A Dzcrx.c346 __io_zcrx_unmap_area(ifq, ifq->areas[area_idx]); in io_zcrx_unmap_areas()
475 struct io_zcrx_area **areas, **old_areas; in io_zcrx_append_area() local
483 old_areas = ifq->areas; in io_zcrx_append_area()
486 areas = kmalloc_array(old_nr + 1, sizeof(areas[0]), in io_zcrx_append_area()
488 if (!areas) in io_zcrx_append_area()
491 memcpy(areas, old_areas, old_nr * sizeof(areas[0])); in io_zcrx_append_area()
492 areas[old_nr] = area; in io_zcrx_append_area()
496 ifq->areas = areas; in io_zcrx_append_area()
667 io_zcrx_free_area(ifq, ifq->areas[i]); in io_zcrx_ifq_free()
676 kfree(ifq->areas); in io_zcrx_ifq_free()
[all …]
/linux/drivers/s390/net/
H A Dctcm_dbug.c46 /* register the areas */ in ctcm_register_dbf_views()
49 ctcm_dbf[x].areas, in ctcm_register_dbf_views()
/linux/arch/mips/include/asm/sn/sn0/
H A Dkldir.h14 * provides pointers to most other IP27 memory areas. This allows us to
15 * resize and/or relocate memory areas at a later time without breaking all
17 * permanently dedicated to areas listed below. Some memory areas (marked
/linux/Documentation/driver-api/mmc/
H A Dmmc-dev-attrs.rst69 areas.
74 size for erasing large areas.
/linux/Documentation/arch/arm/
H A Dmemory.rst96 Please note that mappings which collide with the above areas may result
102 to TASK_SIZE address range. If they wish to access these areas, they
/linux/arch/sparc/include/asm/
H A Deeprom.h8 * for their registers/data areas. The IDPROM lives here too.
/linux/include/dt-bindings/power/
H A Dr8a77995-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a7745-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a77470-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a7791-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a7743-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a7794-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a774c0-sysc.h10 * representing the power areas in the various Interrupt Registers
H A Dr8a7779-sysc.h10 * representing the power areas in the various Interrupt Registers

12345678910>>...15