| /linux/fs/ubifs/ |
| H A 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/tools/perf/tests/shell/ |
| H A D | lock_contention.sh | 2 # kernel lock contention analysis test
12 # Workload to generate lock contention.
42 echo "[Skip] No lock contention tracepoints"
57 echo "Testing perf lock record and perf lock contention"
60 perf lock contention -i ${perfdata} -E 1 -q 2> ${result}
70 echo "Testing perf lock contention --use-bpf"
77 # the perf lock contention output goes to the stderr
88 echo "Testing perf lock record and perf lock contention at the same time"
90 perf lock contention -i- -E 1 -q 2> ${result}
102 echo "Testing perf lock contention
[all...] |
| /linux/tools/perf/Documentation/ |
| H A D | perf-lock.txt | 11 'perf lock' {record|report|script|info|contention}
30 'perf lock contention' shows contention statistics.
40 Output file name for perf lock contention and report.
137 Show per-thread lock contention stat
141 Use BPF program to collect lock contention stats instead of
167 Maximum stack depth when collecting lock contention (default: 8).
178 Show lock contention stat by address
182 Show lock contention stat by owners. This option can be combined with -t,
188 Show lock contention only for given lock types (comma separated list).
199 Show lock contention only for given lock addresses or names (comma separated list).
[all …]
|
| H A D | perf-c2c.txt | 37 for cachelines with highest contention - highest number of HITM accesses.
390 entries that pass the C2C filter, so it is not a pure contention-cycle
|
| /linux/Documentation/locking/ |
| H A 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
|
| H A D | locktorture.rst | 19 different critical region behaviors. The amount of contention on the lock
|
| H A 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
|
| H A 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/tools/perf/scripts/python/bin/ |
| H A D | futex-contention-report | 4 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/futex-contention.py
|
| /linux/kernel/rcu/ |
| H A D | Kconfig | 209 against lock contention. Systems that synchronize their
212 lock contention levels acceptably low. Very large systems
218 skew them, which reduces lock contention enough that large
221 lock contention on the leaf-level rcu_node structures unless
228 kernel boot parameter to avoid contention on the rcu_node
|
| /linux/Documentation/bpf/ |
| H A D | map_hash.rst | 241 depends on the size of the map. Larger batch size reduces lock contention, but
261 contention may impact update operations, though the map type and flags may
262 impact the actual contention on those locks, based on the logic described in
|
| H A D | ringbuf.rst | 67 contention).
|
| /linux/Documentation/trace/ |
| H A 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/Documentation/scheduler/ |
| H A 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/tools/perf/ |
| H A D | builtin-lock.c | 15 #include "util/lock-contention.h"
301 static int select_key(bool contention) in select_key()
306 if (contention) in select_key()
325 static int add_output_field(bool contention, char *name) in add_output_field()
330 if (contention) in add_output_field()
348 static int setup_output_field(bool contention, const char *str) in setup_output_field()
354 if (contention) in setup_output_field()
372 ret = add_output_field(contention, tok); in setup_output_field()
1098 * It can have nested contention begin with mutex spinning, in report_lock_contention_begin_event()
1099 * then we would use the original contention begi in report_lock_contention_begin_event()
299 select_key(bool contention) select_key() argument
323 add_output_field(bool contention,char * name) add_output_field() argument
346 setup_output_field(bool contention,const char * str) setup_output_field() argument
[all...] |
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A 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
301 | lock contention. Here's why: |
319 | acquisition, avoiding this useless contention. |
669 excessive contention for the leaf ``rcu_node`` structures' ``->lock``
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | multigen_lru.rst | 41 theoretically worsen lock contention (mmap_lock). If it is
|
| H A D | slab.rst | 161 (list_lock) where contention may occur.
|
| /linux/Documentation/accounting/ |
| H A D | psi.rst | 13 Without an accurate measure of such contention, users are forced to
|
| /linux/Documentation/userspace-api/ |
| H A D | rseq.rst | 122 critical section to avoid contention on a resource when the thread is
|
| /linux/fs/squashfs/ |
| H A D | Kconfig | 52 it eliminates a memcpy and it also removes the lock contention
|
| /linux/Documentation/core-api/ |
| H A D | swiotlb.rst | 177 trying an allocation, so contention may occur if swiotlb is relatively busy
225 more lock contention.
|
| /linux/Documentation/core-api/real-time/ |
| H A D | hardware.rst | 23 proceed. The impact of this contention varies based on write patterns and the
|
| /linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 55 tuned to deal better with high contention. And for one final thing, it is
|
| /linux/tools/perf/util/ |
| H A D | Build | 135 perf-util-y += lock-contention.o
|