allocations (full) in projects: openbmc

Searched full:allocations (Results 1 – 25 of 1012) sorted by relevance

/openbmc/linux/lib/
H A D	Kconfig.kfence	`33 allocations will be guarded by KFENCE. May be overridden via boot 49 bool "Use a deferrable timer to trigger allocations" 51 Use a deferrable timer to trigger allocations. This avoids forcing 61 bool "Use static keys to set up allocations" if EXPERT 64 Use static keys (static branches) to set up KFENCE allocations. This 82 and allocations/frees. A value of 0 disables stress testing logic.`
H A D	Kconfig.kasan	`89 overhead of ~50% for dynamic allocations. 108 add an overhead of ~20% for dynamic allocations. 180 bool "Check accesses to vmalloc allocations" 183 Makes KASAN check the validity of accesses to vmalloc allocations. 185 With software KASAN modes, all types vmalloc allocations are`
/openbmc/linux/include/linux/
H A D	gfp_types.h	91 * %__GFP_RECLAIMABLE is used for slab allocations that specify 145 * allocations (e.g. %GFP_NOWAIT and %GFP_ATOMIC will ignore them). 167 * of so called costly allocations (with order > %PAGE_ALLOC_COSTLY_ORDER). 168 * !costly allocations are too essential to fail so they are implicitly 189 * Allocations with this flag may fail, but only when there is 190 * genuinely little unused memory. While these allocations do not 208 * Using this flag for costly allocations is _highly_ discouraged. 272 * %GFP_KERNEL is typical for kernel-internal allocations. The caller requires 278 * %GFP_NOWAIT is for kernel allocations that should not stall for direct 294 * %GFP_USER is for userspace allocations that also need to be directly [all …]
/openbmc/linux/Documentation/core-api/
H A D	memory-allocation.rst	41 many other allocations types can use ``GFP_KERNEL``. Note, that 48 ``GFP_NOWAIT`` allocation is likely to fail. Allocations which 52 * Untrusted allocations triggered from userspace should be a subject 55 allocations that should be accounted. 56 * Userspace allocations should use either of the ``GFP_USER``, 72 You may notice that quite a few allocations in the existing code 89 Memory allocations may trigger direct or background reclaim and it is 154 For large allocations you can use vmalloc() and vzalloc(), or directly
H A D	genalloc.rst	`27 allocations is set with min_alloc_order; it is a log-base-2 number like 29 So, if min_alloc_order is passed as 3, then all allocations will be a 44 It's worth noting that, if there are still allocations outstanding from the 60 pool, once again using nid as the node ID for ancillary memory allocations. 63 for DMA allocations. 97 Allocations with gen_pool_alloc_algo() specify an algorithm to be`
H A D	maple_tree.rst	`42 code segment when allocating cannot be done. Allocations of nodes are 91 The allocations are handled by the internal tree code. See 196 Allocations are usually handled internally to the tree, however if allocations 201 unused allocations.`
/openbmc/linux/arch/s390/boot/
H A D	kaslr.c	`162 * Two types of decompressor memory allocations/reserves are considered 165 * "Static" or "single" allocations are done via physmem_alloc_range() and 170 * On the other hand, "dynamic" or "repetitive" allocations are done via 171 * physmem_alloc_top_down(). These allocations are tightly packed together 173 * current position where those allocations start. 176 * only consider "dynamic" allocations by never looking above 177 * physmem_alloc_pos. "Static" allocations, however, are explicitly`
/openbmc/libpldm/src/requester/
H A D	instance-id.c	17 /* We need to track our allocations explicitly due to OFD lock merging/splitting 21 uint32_t allocations; member 49 /* Ensure the underlying file is sized for properly managing allocations in pldm_instance_db_init() 140 if (ctx->state[tid].allocations & BIT(l_iid)) { in pldm_instance_id_alloc() 186 ctx->state[tid].allocations \|= BIT(l_iid); in pldm_instance_id_alloc() 223 if (!(ctx->state[tid].allocations & BIT(iid))) { in pldm_instance_id_free() 238 ctx->state[tid].allocations &= ~BIT(iid); in pldm_instance_id_free()
/openbmc/linux/tools/perf/Documentation/
H A D	examples.txt	`66 well. For example the page allocations done by a 'git gc' can be 77 To check which functions generated page allocations: 120 allocations - to see precisely what kind of page allocations there 157 Or you can observe the whole system's page allocations for 10 173 Or observe how fluctuating the page allocations are, via statistical 190 and check which instructions/source-code generated page allocations: 209 ( this shows that 83.42% of __GI___fork's page allocations come from`
/openbmc/linux/mm/
H A D	Kconfig.debug	`12 bool "Debug page memory allocations" 42 bool "Enable debug page memory allocations by default?" 45 Enable debug page memory allocations by default? This value 49 bool "Debug slab memory allocations" 231 allocations. See Documentation/dev-tools/kmemleak.rst for more 246 Kmemleak must track all the memory allocations to avoid 251 if slab allocations fail.`
H A D	percpu-internal.h	`37 int nr_alloc; /* # of allocations / 148 u64 nr_alloc; / lifetime # of allocations / 150 u64 nr_cur_alloc; / current # of allocations / 151 u64 nr_max_alloc; / max # of live allocations */`
/openbmc/linux/mm/kfence/
H A D	core.c	99 /* Pool usage% threshold when currently covered allocations are skipped. / 136 to gate allocations, to avoid a load and compare if KFENCE is disabled. 145 * allocations of the same source filling up the pool. 147 * Assuming a range of 15%-85% unique allocations in the pool at any point in 184 [KFENCE_COUNTER_ALLOCS] = "total allocations", 186 [KFENCE_COUNTER_ZOMBIES] = "zombie allocations", 188 [KFENCE_COUNTER_SKIP_INCOMPAT] = "skipped allocations (incompatible)", 189 [KFENCE_COUNTER_SKIP_CAPACITY] = "skipped allocations (capacity)", 190 [KFENCE_COUNTER_SKIP_COVERED] = "skipped allocations (covered)", 439 * Note: for allocations made before RNG initialization, will always in kfence_guarded_alloc() [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-memory.json	409 "BriefDescription": "Read Pending Queue Allocations", 413 …"PublicDescription": "Read Pending Queue Allocations : Counts the number of allocations into the R… 418 "BriefDescription": "Read Pending Queue Allocations", 422 …"PublicDescription": "Read Pending Queue Allocations : Counts the number of allocations into the R… 431 … not empty) and the average latency (in conjunction with the number of allocations). The RPQ is u… 439 … not empty) and the average latency (in conjunction with the number of allocations). The RPQ is u… 477 "BriefDescription": "Write Pending Queue Allocations", 481 …"PublicDescription": "Write Pending Queue Allocations : Counts the number of allocations into the … 486 "BriefDescription": "Write Pending Queue Allocations", 490 …"PublicDescription": "Write Pending Queue Allocations : Counts the number of allocations into the … [all …]
/openbmc/linux/Documentation/dev-tools/
H A D	kfence.rst	39 sample interval determines the frequency with which heap allocations will be 44 The sample interval controls a timer that sets up KFENCE allocations. By 57 further KFENCE allocations occur. With ``CONFIG_KFENCE_NUM_OBJECTS`` (default 242 Guarded allocations are set up based on the sample interval. After expiration 248 When using ``CONFIG_KFENCE_STATIC_KEYS=y``, KFENCE allocations are "gated" 290 coverage of allocations, KFENCE limits currently covered allocations of the 293 limits frequent long-lived allocations (e.g. pagecache) of the same source 296 at which to start limiting currently covered allocations can be configured via 303 page handling code to set up and deal with KFENCE allocations.
/openbmc/linux/Documentation/mm/
H A D	numa.rst	`80 memory, Linux must decide whether to order the zonelists such that allocations 122 So, default, local allocations will succeed with the kernel supplying the 124 allows such allocations to fallback to other nearby nodes when a node that 127 Some kernel allocations do not want or cannot tolerate this allocation fallback 148 allocations will be attempted.`
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-interconnect.json	266 …"PublicDescription": "Counts the number of allocations into the AK Ingress. This queue is where t… 282 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 306 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 330 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 495 …witch (towards the devices). This can be used in conjunction with the allocations event in order … 994 "BriefDescription": "Rx Flit Buffer Allocations", 998 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1002 "BriefDescription": "Rx Flit Buffer Allocations - DRS; for VN0", 1006 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1011 "BriefDescription": "Rx Flit Buffer Allocations - DRS; for VN1", [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-interconnect.json	266 …"PublicDescription": "Counts the number of allocations into the AK Ingress. This queue is where t… 282 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 306 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 330 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 495 …witch (towards the devices). This can be used in conjunction with the allocations event in order … 995 "BriefDescription": "Rx Flit Buffer Allocations", 999 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1003 "BriefDescription": "Rx Flit Buffer Allocations - DRS; for VN0", 1007 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1012 "BriefDescription": "Rx Flit Buffer Allocations - DRS; for VN1", [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	129 …"PublicDescription": "Counts the number of allocations into the AK Ingress. This queue is where t… 151 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 173 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 195 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 296 …witch (towards the devices). This can be used in conjuection with the allocations event in order … 1020 "BriefDescription": "Rx Flit Buffer Allocations", 1024 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1028 "BriefDescription": "Rx Flit Buffer Allocations - DRS", 1032 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 1036 "BriefDescription": "Rx Flit Buffer Allocations - DRS; for VN0", [all …]
/openbmc/linux/drivers/gpu/drm/ttm/tests/
H A D	ttm_device_test.c	`121 .description = "No DMA allocations, no DMA32 required", 127 .description = "DMA allocations, DMA32 required", 133 .description = "No DMA allocations, DMA32 required", 139 .description = "DMA allocations, no DMA32 required",`
/openbmc/linux/arch/arm/mach-davinci/
H A D	sram.h	`10 /* ARBITRARY: SRAM allocations are multiples of this 2^N size / 14 SRAM allocations return a CPU virtual address, or NULL on error.`
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-cache.json	351 "BriefDescription": "Ingress Allocations; IPQ", 355 … "PublicDescription": "Counts number of allocations per cycle into the specified Ingress queue.", 360 "BriefDescription": "Ingress Allocations; IRQ", 364 … "PublicDescription": "Counts number of allocations per cycle into the specified Ingress queue.", 369 "BriefDescription": "Ingress Allocations; IRQ Rejected", 373 … "PublicDescription": "Counts number of allocations per cycle into the specified Ingress queue.", 378 "BriefDescription": "Ingress Allocations; VFIFO", 382 … "PublicDescription": "Counts number of allocations per cycle into the specified Ingress queue.", 766 "BriefDescription": "Egress Allocations; AD - Cachebo", 770 …"PublicDescription": "Number of allocations into the Cbo Egress. The Egress is used to queue up r… [all …]
H A D	uncore-interconnect.json	129 …"PublicDescription": "Counts the number of allocations into the AK Ingress. This queue is where t… 151 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 173 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 195 …"PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where t… 287 …witch (towards the devices). This can be used in conjunction with the allocations event in order … 615 "BriefDescription": "Rx Flit Buffer Allocations", 619 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 623 "BriefDescription": "Rx Flit Buffer Allocations - DRS", 627 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 631 "BriefDescription": "Rx Flit Buffer Allocations - HOM", [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-memory.json	1196 "BriefDescription": "AD Ingress (from CMS) : AD Ingress (from CMS) Allocations", 1206 "BriefDescription": "AD Ingress (from CMS) : AD Ingress (from CMS) Allocations", 1221 "BriefDescription": "BL Ingress (from CMS) : BL Ingress (from CMS) Allocations", 1232 "BriefDescription": "BL Ingress (from CMS) : BL Ingress (from CMS) Allocations", 1294 "BriefDescription": "AD Egress (to CMS) : AD Egress (to CMS) Allocations", 1305 "BriefDescription": "AD Egress (to CMS) : AD Egress (to CMS) Allocations", 1936 "BriefDescription": "Read Pending Queue Allocations", 1940 …"PublicDescription": "Read Pending Queue Allocations: Counts the number of allocations into the Re… 1945 "BriefDescription": "Read Pending Queue Allocations", 1949 …"PublicDescription": "Read Pending Queue Allocations: Counts the number of allocations into the Re… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-interconnect.json	517 "BriefDescription": "AK Egress Allocations", 623 …witch (towards the devices). This can be used in conjunction with the allocations event in order … 2030 "BriefDescription": "BL Ingress (from CMS) Allocations", 2197 "BriefDescription": "Transgress Ingress Allocations; AD - Bounce", 2201 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2206 "BriefDescription": "Transgress Ingress Allocations; AD - Credit", 2210 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2215 "BriefDescription": "Transgress Ingress Allocations; AK - Bounce", 2219 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2224 "BriefDescription": "Transgress Ingress Allocations; BL - Bounce", [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-interconnect.json	517 "BriefDescription": "AK Egress Allocations", 623 …witch (towards the devices). This can be used in conjunction with the allocations event in order … 1964 "BriefDescription": "BL Ingress (from CMS) Allocations", 2131 "BriefDescription": "Transgress Ingress Allocations; AD - Bounce", 2135 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2140 "BriefDescription": "Transgress Ingress Allocations; AD - Credit", 2144 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2149 "BriefDescription": "Transgress Ingress Allocations; AK - Bounce", 2153 …"PublicDescription": "Number of allocations into the CMS Ingress The Ingress is used to queue up … 2158 "BriefDescription": "Transgress Ingress Allocations; BL - Bounce", [all …]

12 3 4 5 6 7 8 9 10 >>...41

Project(s)

Full Search
Definition
Symbol
File Path
History
Type