| /tools/perf/scripts/perl/ |
| A D | rw-by-pid.pl | 21 my %reads;
31 $reads{$common_pid}{bytes_read} += $ret;
33 if (!defined ($reads{$common_pid}{bytes_read})) {
34 $reads{$common_pid}{bytes_read} = 0;
36 $reads{$common_pid}{errors}{$ret}++;
47 $reads{$common_pid}{total_reads}++;
48 $reads{$common_pid}{comm} = $common_comm;
83 ($reads{$a}{bytes_read} || 0) } keys %reads) {
84 my $comm = $reads{$pid}{comm} || "";
101 foreach my $pid (keys %reads) {
[all …]
|
| A D | rwtop.pl | 27 my %reads;
44 $reads{$common_pid}{bytes_read} += $ret;
46 if (!defined ($reads{$common_pid}{bytes_read})) {
47 $reads{$common_pid}{bytes_read} = 0;
49 $reads{$common_pid}{errors}{$ret}++;
62 $reads{$common_pid}{total_reads}++;
63 $reads{$common_pid}{comm} = $common_comm;
137 ($reads{$a}{bytes_read} || 0) } keys %reads) {
138 my $comm = $reads{$pid}{comm} || "";
141 my $bytes_read = $reads{$pid}{bytes_read} || 0;
[all …]
|
| A D | rw-by-file.pl | 25 my %reads;
34 $reads{$fd}{bytes_requested} += $count;
35 $reads{$fd}{total_reads}++;
57 foreach my $fd (sort {$reads{$b}{bytes_requested} <=>
58 $reads{$a}{bytes_requested}} keys %reads) {
59 my $total_reads = $reads{$fd}{total_reads};
60 my $bytes_requested = $reads{$fd}{bytes_requested};
|
| /tools/memory-model/litmus-tests/ |
| A D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 7 * when there is but one non-reads-from (AKA non-rf) link, does not suffice
8 * if there is more than one. Of the three processes, only P1() reads from
11 * to P0() is a read-to-write link (AKA a "from-reads" or just "fr" link).
|
| A D | IRIW+poonceonces+OnceOnce.litmus | 6 * Test of independent reads from independent writes with nothing
7 * between each pairs of reads. In other words, is anything at all
|
| A D | IRIW+fencembonceonces+OnceOnce.litmus | 6 * Test of independent reads from independent writes with smp_mb()
7 * between each pairs of reads. In other words, is smp_mb() sufficient to
|
| A D | ISA2+pooncerelease+poacquirerelease+poacquireonce.litmus | 9 * case (P2() to P0()), each process reads from the preceding process's
10 * write. In memory-model-speak, there is only one non-reads-from
|
| A D | README | 7 successive reads from the same variable are ordered.
24 Test of independent reads from independent writes with smp_mb()
25 between each pairs of reads. In other words, is smp_mb()
32 Test of independent reads from independent writes with nothing
33 between each pairs of reads. In other words, is anything at all
54 load-buffering litmus test, where each process reads from one
59 litmus test, where each process reads from one of two variables then
104 process writes data and then a flag, and the other process reads
217 reads-from link (rf) and internal to the P0() process. This is
218 "rfi", which is an abbreviation for "reads-from internal". Because
[all …]
|
| A D | CoRR+poonceonce+Once.litmus | 7 * reads from the same variable are ordered.
|
| A D | LB+poacquireonce+pooncerelease.litmus | 7 * test, where each process reads from one of two variables then writes
|
| A D | SB+poonceonces.litmus | 8 * variable that the preceding process reads.
|
| A D | SB+fencembonceonces.litmus | 8 * variable that the preceding process reads. (Locking and RCU can also
|
| /tools/perf/Documentation/ |
| A D | guest-files.txt | 4 Guest OS /proc/kallsyms file copy. perf reads it to get guest
8 Guest OS /proc/modules file copy. perf reads it to get guest
|
| A D | perf-iostat.txt | 22 - Outbound Read - CPU reads from I/O devices below root port, in MB
|
| A D | perf-timechart.txt | 28 Upper bar shows incoming events (disk reads, ingress network packets).
|
| /tools/memory-model/Documentation/ |
| A D | glossary.txt | 36 to that same variable, (in other words, the acquire load "reads
52 See also "From-reads" and "Reads-from".
107 load from that same variable, there is said to be a from-reads
110 It is also possible to have a from-reads link within a CPU, which
111 is a "from-reads internal" (fri) link. The term "from-reads
138 smp_store_release() pairs with an smp_load_acquire() that reads
144 CPU, there is said to be a reads-from link from the second
149 coherence and from-reads links.
151 It is also possible to have a reads-from link within a CPU, which
152 is a "reads-from internal" (rfi) link. The term "reads-from
[all …]
|
| A D | access-marking.txt | 73 2. Data-racy reads whose values are checked against marked reload.
88 reads can enable better checking of the remaining accesses implementing
90 prevents any non-diagnostic reads from shared variable x from running
92 to x allows KCSAN to detect reads from x from within regions of code
94 data_race() for the diagnostic reads because otherwise KCSAN would give
95 false-positive warnings about these diagnostic reads.
109 The values from some reads are not implicitly trusted. They are instead
133 Values from some reads feed into heuristics that can tolerate occasional
158 due to compiler-mangled reads, it can also tolerate the occasional
490 flag any concurrent plain C-language reads from foo, and given
[all …]
|
| A D | recipes.txt | 51 holding the update-side lock, reads from that variable
56 when running during early boot, reads from that variable
360 each load reads the value written by the other CPU's store. In the
535 1. Write-to-read, where the next CPU reads the value that the
538 relation is called "reads-from" and is usually abbreviated "rf".
543 often called "from-reads" and is sometimes abbreviated "fr".
|
| A D | explanation.txt | 136 reads flag into the private variable r1, and if it is set, reads the
449 values of multiple reads.
547 write. In colloquial terms, the load "reads from" the store. We
550 the same CPU (internal reads-from, or rfi) and where they occur on
551 different CPUs (external reads-from, or rfe).
645 is a store, then the store which R reads from must come before
770 the write which R reads from is co-before W. In symbols,
951 each load between the store that it reads from and the following
1106 store and a second, po-later load reads from that store:
1361 store to flag propagates to P1 before P1 reads flag.
[all …]
|
| A D | ordering.txt | 195 smp_wmb(); // BUG: does not order the reads!!!
277 To see the performance advantages, suppose that the above example reads
467 o Marked reads, such as READ_ONCE() and atomic_read(). These
472 reorder marked reads with each other or with other unordered
534 to a given variable are reads.
|
| /tools/testing/selftests/coredump/ |
| A D | README.rst | 21 reads zero. But when the thread is dead (e.g. during a coredump), this field should have valid
45 reads the stack pointers of all threads of crashed processes.
|
| /tools/testing/selftests/resctrl/ |
| A D | resctrl_val.c | 306 float reads = 0, of_mul_read = 1; in get_read_mem_bw_imc() local
331 reads += r->return_value.value * of_mul_read * SCALE; in get_read_mem_bw_imc()
334 *bw_imc = reads; in get_read_mem_bw_imc()
|
| /tools/lib/perf/Documentation/ |
| A D | libperf-sampling.txt | 44 - reads and displays recorded samples
169 Following code walks through the ring buffers and reads stored events/samples:
|
| A D | libperf-counting.txt | 37 * reads and displays event counts
|
| /tools/perf/tests/shell/attr/ |
| A D | README | 27 This is the python script that does all the hard work. It reads
|