| /tools/perf/scripts/perl/ |
| 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}++;
46 $reads{$common_pid}{bytes_requested} += $count;
47 $reads{$common_pid}{total_reads}++;
48 $reads{$common_pid}{comm} = $common_comm;
82 foreach my $pid (sort { ($reads{$b}{bytes_read} || 0) <=>
83 ($reads{$a}{bytes_read} || 0) } keys %reads) {
[all …]
|
| 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}++;
61 $reads{$common_pid}{bytes_requested} += $count;
62 $reads{$common_pid}{total_reads}++;
63 $reads{$common_pid}{comm} = $common_comm;
136 foreach my $pid (sort { ($reads{$b}{bytes_read} || 0) <=>
137 ($reads{$a}{bytes_read} || 0) } keys %reads) {
[all …]
|
| 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/io_uring/ |
| D | io_uring-cp.c | 125 unsigned long reads, writes; in copy_file() local
131 writes = reads = offset = 0; in copy_file()
139 had_reads = reads; in copy_file()
143 if (reads + writes >= QD) in copy_file()
155 reads++; in copy_file()
158 if (had_reads != reads) { in copy_file()
218 reads--; in copy_file()
|
| D | README | 13 Benchmark program that does random reads on a number of files. This
|
| /tools/memory-model/litmus-tests/ |
| 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).
|
| 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
|
| 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
|
| 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
|
| 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
96 process writes data and then a flag, and the other process reads
175 the other process reads from these same variables, the corresponding
209 reads-from link (rf) and internal to the P0() process. This is
[all …]
|
| D | CoRR+poonceonce+Once.litmus | 7 * reads from the same variable are ordered.
|
| D | LB+poacquireonce+pooncerelease.litmus | 7 * test, where each process reads from one of two variables then writes
|
| D | SB+poonceonces.litmus | 8 * variable that the preceding process reads.
|
| D | SB+fencembonceonces.litmus | 8 * variable that the preceding process reads. (Locking and RCU can also
|
| /tools/memory-model/Documentation/ |
| 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
147 which means that algorithms using reads-from links can use lighter
149 coherence and from-reads links.
151 It is also possible to have a reads-from link within a CPU, which
[all …]
|
| D | access-marking.txt | 67 2. Data-racy reads whose values are checked against marked reload.
78 values are ignored, and other situations where reads from shared variables
82 reads can enable better checking of the remaining accesses implementing
84 prevents any non-diagnostic reads from shared variable x from running
86 to x allows KCSAN to detect reads from x from within regions of code
88 data_race() for the diagnostic reads because otherwise KCSAN would give
89 false-positive warnings about these diagnostic reads.
103 The values from some reads are not implicitly trusted. They are instead
127 Values from some reads feed into heuristics that can tolerate occasional
128 errors. Such reads can use data_race(), thus allowing KCSAN to focus on
[all …]
|
| D | recipes.txt | 51 holding the update-side lock, reads from that variable
56 when running during early boot, reads from that variable
356 each load reads the value written by the other CPU's store. In the
531 1. Write-to-read, where the next CPU reads the value that the
534 relation is called "reads-from" and is usually abbreviated "rf".
539 often called "from-reads" and is sometimes abbreviated "fr".
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-record_parse.txt | 34 It reads the "common_type" field. The _tep_ argument is the trace event parser
38 It reads the "common_pid" field. The _tep_ argument is the trace event parser
42 record _rec_. It reads the "common_preempt_count" field. The _tep_ argument is
46 It reads the "common_flags" field. The _tep_ argument is the trace event parser
|
| D | libtraceevent-field_read.txt | 19 The _tep_read_number_field()_ function reads the value of the _field_ from the
|
| D | libtraceevent-endian_read.txt | 19 The _tep_read_number()_ function reads an integer from raw data, taking into
|
| /tools/testing/selftests/resctrl/ |
| D | resctrl_val.c | 307 float reads, writes, of_mul_read, of_mul_write; in get_mem_bw_imc() local
311 reads = 0, writes = 0, of_mul_read = 1, of_mul_write = 1; in get_mem_bw_imc()
367 reads += r->return_value.value * of_mul_read * SCALE; in get_mem_bw_imc()
377 *bw_imc = reads; in get_mem_bw_imc()
386 *bw_imc = reads + writes; in get_mem_bw_imc()
|
| /tools/perf/Documentation/ |
| D | perf-iostat.txt | 22 - Outbound Read - CPU reads from I/O devices below root port, in MB
|
| D | perf-kvm.txt | 90 Guest os /proc/kallsyms file copy. 'perf' kvm' reads it to get guest
93 Guest os /proc/modules file copy. 'perf' kvm' reads it to get guest
|
| D | perf-inject.txt | 15 perf-inject reads a perf-record event stream and repipes it to stdout. At any
|
| /tools/lib/perf/Documentation/ |
| D | libperf-sampling.txt | 44 - reads and displays recorded samples
169 Following code walks through the ring buffers and reads stored events/samples:
|