Searched refs:writes (Results 1 – 22 of 22) sorted by relevance
/tools/perf/scripts/perl/ |
D | rw-by-pid.pl | 22 my %writes; 58 $writes{$common_pid}{errors}{$ret}++; 68 $writes{$common_pid}{bytes_written} += $count; 69 $writes{$common_pid}{total_writes}++; 70 $writes{$common_pid}{comm} = $common_comm; 123 foreach my $pid (sort { ($writes{$b}{bytes_written} || 0) <=> 124 ($writes{$a}{bytes_written} || 0)} keys %writes) { 125 my $comm = $writes{$pid}{comm} || ""; 126 my $total_writes = $writes{$pid}{total_writes} || 0; 127 my $bytes_written = $writes{$pid}{bytes_written} || 0; [all …]
|
D | rwtop.pl | 28 my %writes; 75 $writes{$common_pid}{errors}{$ret}++; 87 $writes{$common_pid}{bytes_written} += $count; 88 $writes{$common_pid}{total_writes}++; 89 $writes{$common_pid}{comm} = $common_comm; 160 foreach my $pid (sort { ($writes{$b}{bytes_written} || 0) <=> 161 ($writes{$a}{bytes_written} || 0)} keys %writes) { 162 my $comm = $writes{$pid}{comm} || ""; 163 my $total_writes = $writes{$pid}{total_writes} || 0; 164 my $bytes_written = $writes{$pid}{bytes_written} || 0; [all …]
|
D | rw-by-file.pl | 26 my %writes; 45 $writes{$fd}{bytes_written} += $count; 46 $writes{$fd}{total_writes}++; 69 foreach my $fd (sort {$writes{$b}{bytes_written} <=> 70 $writes{$a}{bytes_written}} keys %writes) { 71 my $total_writes = $writes{$fd}{total_writes}; 72 my $bytes_written = $writes{$fd}{bytes_written};
|
/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() 143 if (reads + writes >= QD) in copy_file() 219 writes++; in copy_file() 222 writes--; in copy_file() 229 while (writes) { in copy_file() 243 writes--; in copy_file()
|
/tools/memory-model/litmus-tests/ |
D | IRIW+poonceonces+OnceOnce.litmus | 6 * Test of independent reads from independent writes with nothing 9 * of a pair of writes, where each write is to a different variable by a
|
D | IRIW+fencembonceonces+OnceOnce.litmus | 6 * Test of independent reads from independent writes with smp_mb() 9 * of writes, where each write is to a different variable by a different
|
D | CoWW+poonceonce.litmus | 7 * writes to 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 | 7 * to order the store-buffering pattern, where each process writes to the
|
D | README | 21 successive writes to the same variable are ordered. 24 Test of independent reads from independent writes with smp_mb() 27 the order of a pair of writes, where each write is to a different 32 Test of independent reads from independent writes with nothing 35 order of a pair of writes, where each write is to a different 55 of two variables then writes to the other? 60 writes to the other? 96 process writes data and then a flag, and the other process reads 174 For example, if the one process writes to a pair of variables, and
|
D | SB+fencembonceonces.litmus | 7 * order the store-buffering pattern, where each process writes to the
|
/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() 368 writes += w->return_value.value * of_mul_write * SCALE; in get_mem_bw_imc() 382 *bw_imc = writes; in get_mem_bw_imc() 386 *bw_imc = reads + writes; in get_mem_bw_imc()
|
/tools/memory-model/Documentation/ |
D | access-marking.txt | 85 concurrently with updates to x. Then using plain C-language writes 149 for example, from sysfs. This means that some code in sysfs writes 150 to this same variable, and these writes can also use data_race(). 195 b. When the store writes the value already contained in 230 and data_race() writes on the other, KCSAN will not report the location 231 of these data_race() writes. 289 buggy lockless writes, read_foo_diagnostic() can be updated as follows: 304 However, in order for KCSAN to detect buggy lockless writes, your kernel 469 C-language writes to foo. 513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
D | simple.txt | 142 in read-side code". Yes, you can do writes from within sequence-locking 143 readers, but it won't be so simple. For example, such writes will be 215 only for heuristics, or if they are frequently executed writes that
|
D | control-dependencies.txt | 196 the writes to "b" with the condition. Unfortunately for this line 197 of reasoning, the compiler might compile the two writes to "b" as
|
D | ordering.txt | 199 Therefore, if you need to use smp_wmb() with unmarked C-language writes, 459 o Marked writes, such as WRITE_ONCE() and atomic_set(). These 464 reorder marked writes with each other or with other unordered
|
D | recipes.txt | 57 need not use READ_ONCE() and writes to that variable
|
D | explanation.txt | 1066 allowing out-of-order writes like this to occur. The model avoided
|
/tools/perf/Documentation/ |
D | perf-iostat.txt | 24 - Outbound Write - CPU writes to I/O devices below root port, in MB
|
D | perf-timechart.txt | 29 Lower bar shows outgoing events (disk writes, egress network packets).
|
/tools/lib/traceevent/Documentation/ |
D | libtraceevent-event_print.txt | 22 _record_ and writes it into the trace sequence _s_, according to the format
|
/tools/memory-model/ |
D | linux-kernel.cat | 163 (* Warn about plain writes and marked accesses in the same region *)
|