Home
last modified time | relevance | path

Searched refs:reads (Results 1 – 25 of 385) sorted by relevance

12345678910>>...16

/linux-6.1.9/tools/perf/scripts/perl/
Drw-by-pid.pl21 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 …]
Drwtop.pl27 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 …]
Drw-by-file.pl25 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};
/linux-6.1.9/drivers/gpu/drm/nouveau/nvif/
Dtimer.c30 if (wait->reads == 0) { in nvif_timer_wait_test()
36 if (WARN_ON(wait->reads++ == 16)) in nvif_timer_wait_test()
40 wait->reads = 1; in nvif_timer_wait_test()
55 wait->reads = 0; in nvif_timer_wait_init()
/linux-6.1.9/drivers/input/touchscreen/
Dzylonite-wm97xx.c32 u8 reads; /* number of coord reads per read cycle */ member
88 int reads = 0; in wm97xx_acc_pen_down() local
110 if (reads) in wm97xx_acc_pen_down()
132 reads++; in wm97xx_acc_pen_down()
133 } while (reads < cinfo[sp_idx].reads); in wm97xx_acc_pen_down()
Dmainstone-wm97xx.c38 u8 reads; /* number of coord reads per read cycle */ member
118 int reads = 0; in wm97xx_acc_pen_down() local
140 if (reads) in wm97xx_acc_pen_down()
162 reads++; in wm97xx_acc_pen_down()
163 } while (reads < cinfo[sp_idx].reads); in wm97xx_acc_pen_down()
/linux-6.1.9/tools/io_uring/
Dio_uring-cp.c125 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()
/linux-6.1.9/tools/memory-model/Documentation/
Dglossary.txt36 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 …]
Daccess-marking.txt67 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 …]
/linux-6.1.9/Documentation/admin-guide/device-mapper/
Ddelay.rst5 Device-Mapper's "delay" target delays reads and/or writes
13 With separate write parameters, the first set is only used for reads.
30 # splitting reads and writes to different devices $1 $2
/linux-6.1.9/tools/memory-model/litmus-tests/
DZ6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus7 * 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).
DREADME7 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
183 the other process reads from these same variables, the corresponding
217 reads-from link (rf) and internal to the P0() process. This is
[all …]
DIRIW+poonceonces+OnceOnce.litmus6 * Test of independent reads from independent writes with nothing
7 * between each pairs of reads. In other words, is anything at all
DIRIW+fencembonceonces+OnceOnce.litmus6 * Test of independent reads from independent writes with smp_mb()
7 * between each pairs of reads. In other words, is smp_mb() sufficient to
DISA2+pooncerelease+poacquirerelease+poacquireonce.litmus9 * 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
/linux-6.1.9/drivers/gpu/drm/nouveau/nvkm/subdev/timer/
Dbase.c32 if (wait->reads == 0) { in nvkm_timer_wait_test()
38 if (wait->reads++ == 16) { in nvkm_timer_wait_test()
44 wait->reads = 1; in nvkm_timer_wait_test()
59 wait->reads = 0; in nvkm_timer_wait_init()
/linux-6.1.9/arch/riscv/include/asm/
Dio.h94 __io_reads_ins(reads, u8, b, __io_br(), __io_ar(addr))
95 __io_reads_ins(reads, u16, w, __io_br(), __io_ar(addr))
96 __io_reads_ins(reads, u32, l, __io_br(), __io_ar(addr))
123 __io_reads_ins(reads, u64, q, __io_br(), __io_ar(addr))
/linux-6.1.9/Documentation/block/
Dkyber-iosched.rst6 reads and synchronous writes. Kyber will throttle requests in order to meet
11 Target latency for reads (in nanoseconds).
Ddeadline-iosched.rst50 device dispatch queue, we always give a preference to reads. However, we
52 how many times we give preference to reads over writes. When that has been
54 same criteria as reads.
/linux-6.1.9/tools/perf/Documentation/
Dguest-files.txt4 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
/linux-6.1.9/Documentation/admin-guide/
Diostats.rst65 Field 1 -- # of reads completed (unsigned long)
66 This is the total number of reads completed successfully.
68 Field 2 -- # of reads merged, field 6 -- # of writes merged (unsigned long)
70 efficiency. Thus two 4K reads may become one 8K read before it is
78 This is the total number of milliseconds spent by all reads (as
161 Field 1 -- # of reads issued
162 This is the total number of reads issued to this partition.
178 words, the number of reads for partitions is counted slightly before time
183 reads/writes before merges for partitions and after for disks. Since a
185 the number of reads/writes issued can be several times higher than the
[all …]
/linux-6.1.9/tools/lib/traceevent/Documentation/
Dlibtraceevent-record_parse.txt34 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
/linux-6.1.9/Documentation/ABI/testing/
Dprocfs-diskstats13 4 reads completed successfully
14 5 reads merged
Dsysfs-devices-platform-docg39 The protection has information embedded whether it blocks reads,
26 The protection has information embedded whether it blocks reads,
/linux-6.1.9/drivers/input/joystick/
Dguillemot.c51 int reads; member
109 guillemot->reads++; in guillemot_poll()
249 …printk(KERN_INFO "guillemot.c: Failed %d reads out of %d on %s\n", guillemot->reads, guillemot->ba… in guillemot_disconnect()

12345678910>>...16