| /linux-6.1.9/fs/ubifs/ |
| D | shrinker.c | 58 static int shrink_tnc(struct ubifs_info *c, int nr, int age, int *contention) in shrink_tnc() argument
108 *contention = 1; in shrink_tnc()
144 static int shrink_tnc_trees(int nr, int age, int *contention) in shrink_tnc_trees() argument
167 *contention = 1; in shrink_tnc_trees()
177 *contention = 1; in shrink_tnc_trees()
187 freed += shrink_tnc(c, nr, age, contention); in shrink_tnc_trees()
283 int contention = 0; in ubifs_shrink_scan() local
299 freed = shrink_tnc_trees(nr, OLD_ZNODE_AGE, &contention); in ubifs_shrink_scan()
304 freed += shrink_tnc_trees(nr - freed, YOUNG_ZNODE_AGE, &contention); in ubifs_shrink_scan()
309 freed += shrink_tnc_trees(nr - freed, 0, &contention); in ubifs_shrink_scan()
[all …]
|
| /linux-6.1.9/tools/perf/Documentation/ |
| D | perf-lock.txt | 11 'perf lock' {record|report|script|info|contention}
30 'perf lock contention' shows contention statistics.
134 Show per-thread lock contention stat
138 Use BPF program to collect lock contention stats instead of
162 Maximum stack depth when collecting lock contention (default: 8).
|
| D | perf-c2c.txt | 33 for cachelines with highest contention - highest number of HITM accesses.
|
| /linux-6.1.9/Documentation/locking/ |
| D | lockstat.rst | 14 Because things like lock contention can severely impact performance.
51 - number of lock contention that involved x-cpu data
80 It also tracks 4 contention points per class. A contention point is a call site
143 short separator (line 08, 13) from the contention points.
145 Lines 09-12 show the first 4 recorded contention points (the code
151 short separator. The contention points don't match the column descriptors,
152 they have two: contentions and [<IP>] symbol. The second set of contention
|
| D | locktorture.rst | 19 different critical region behaviors. The amount of contention on the lock
|
| D | ww-mutex-design.rst | 352 contention for a new lock and hence a true chance of deadlock. In that
360 In general, not much contention is expected. The locks are typically used to
|
| D | rt-mutex-design.rst | 428 If there is contention on the lock, we go about the slow path
442 contention).
518 CMPXCHG. Since the taking of a mutex on contention always sets the
|
| /linux-6.1.9/tools/perf/scripts/python/bin/ |
| D | futex-contention-report | 4 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/futex-contention.py
|
| /linux-6.1.9/tools/perf/tests/shell/ |
| D | lock_contention.sh | 42 perf lock contention -i ${perfdata} -E 1 -q 2> ${result}
|
| /linux-6.1.9/kernel/rcu/ |
| D | Kconfig | 175 against lock contention. Systems that synchronize their
178 lock contention levels acceptably low. Very large systems
184 skew them, which reduces lock contention enough that large
187 lock contention on the leaf-level rcu_node structures unless
194 kernel boot parameter to avoid contention on the rcu_node
|
| /linux-6.1.9/tools/perf/ |
| D | builtin-lock.c | 297 static int select_key(bool contention) in select_key() argument
302 if (contention) in select_key()
321 static int add_output_field(bool contention, char *name) in add_output_field() argument
326 if (contention) in add_output_field()
344 static int setup_output_field(bool contention, const char *str) in setup_output_field() argument
350 if (contention) in setup_output_field()
368 ret = add_output_field(contention, tok); in setup_output_field()
|
| /linux-6.1.9/kernel/ |
| D | Kconfig.hz | 14 contention and cacheline bounces as a result of timer interrupts.
|
| /linux-6.1.9/Documentation/trace/ |
| D | events-kmem.rst | 72 contention on the lruvec->lru_lock.
82 for order-0 pages, reduces contention on the zone->lock and reduces the
|
| /linux-6.1.9/Documentation/scheduler/ |
| D | schedutil.rst | 38 two metrics are the same, but once there is contention for the CPU 'running'
40 while 'runnable' will increase to reflect the amount of contention.
|
| /linux-6.1.9/Documentation/mm/ |
| D | split_page_table_lock.rst | 9 multi-threaded applications due high contention on the lock. To improve
|
| /linux-6.1.9/Documentation/networking/ |
| D | scaling.rst | 195 during CPU contention by dropping packets from large flows slightly
214 and cache contention) and toggled per CPU by setting the relevant bit
409 provides two benefits. First, contention on the device queue lock is
411 (contention can be eliminated completely if each CPU has its own
489 experience no contention. If there are fewer queues than CPUs, then the
|
| /linux-6.1.9/Documentation/devicetree/bindings/sound/ |
| D | cs35l36.txt | 34 port to prevent bus contention on the output signal
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | multigen_lru.rst | 41 theoretically worsen lock contention (mmap_lock). If it is
|
| /linux-6.1.9/Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.txt | 78 drive the data bus after OE is de-asserted, in order to avoid contention on
|
| /linux-6.1.9/drivers/gpu/drm/ |
| D | Kconfig | 110 bool "Enable backtrace history for lock contention"
118 contention. A history of each drm modeset lock path hitting -EDEADLK
|
| /linux-6.1.9/Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 67 | leaf ``rcu_node`` structures have fanout of 64, the contention on |
76 | if you are using such a system and running into contention problems |
111 contention remains roughly constant up the tree. No matter how many CPUs
114 thus ensuring that the lock contention on that root ``rcu_node``
118 lock contention under control at all tree levels regardless of the level
636 excessive contention for the leaf ``rcu_node`` structures' ``->lock``
|
| /linux-6.1.9/Documentation/arm/ |
| D | vlocks.rst | 148 reducing bus contention in contended cases.
|
| /linux-6.1.9/Documentation/accounting/ |
| D | psi.rst | 13 Without an accurate measure of such contention, users are forced to
|
| /linux-6.1.9/drivers/block/paride/ |
| D | Transition-notes | 113 that the only possible contention is between scheduling ps_tq followed by
|
| /linux-6.1.9/fs/squashfs/ |
| D | Kconfig | 52 it eliminates a memcpy and it also removes the lock contention
|