Home
last modified time | relevance | path

Searched refs:writes (Results 1 – 25 of 311) sorted by relevance

12345678910>>...13

/Linux-v4.19/tools/perf/scripts/perl/
Drw-by-pid.pl22 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 …]
Drwtop.pl28 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 …]
Drw-by-file.pl26 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};
/Linux-v4.19/Documentation/
Dio_ordering.txt2 Ordering I/O writes to memory-mapped addresses
6 platforms, driver writers are responsible for ensuring that I/O writes to
9 chipset to flush pending writes to the device before any reads are posted. A
12 subsequent writes to I/O space arrived only after all prior writes (much like a
50 pending writes before actually posting the read to the chipset, preventing
Diostats.txt67 Field 2 -- # of reads merged, field 6 -- # of writes merged
68 Reads and writes which are adjacent to each other may be merged for
80 Field 5 -- # of writes completed
81 This is the total number of writes completed successfully.
83 Field 6 -- # of writes merged
90 This is the total number of milliseconds spent by all writes (as
151 Field 3 -- # of writes issued
152 This is the total number of writes issued to this partition.
166 reads/writes before merges for partitions and after for disks. Since a
168 the number of reads/writes issued can be several times higher than the
[all …]
/Linux-v4.19/Documentation/filesystems/
Dfuse-io.txt11 In direct-io mode the page cache is completely bypassed for reads and writes.
16 after any writes to the file. All mmap modes are supported.
18 The cached mode has two sub modes controlling how writes are handled. The
25 uncached, but fully written pages). No READ requests are ever sent for writes,
28 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
Dudf.txt9 dvd+rw drives and media support true random sector writes, and so a udf
14 and read-modify-write cycles to allow the filesystem random sector writes
15 while providing the hardware with only full packet writes. While not
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-block-bcache55 Sum of all reads and writes that have bypassed the cache (due
64 writes will be buffered in the cache. When off, caching is in
65 writethrough mode; reads and writes will be added to the
74 used to buffer writes until it is mostly full, at which point
75 writes transparently revert to writethrough mode. Intended only
94 place and reducing total number of writes sent to the backing
102 switched on and off. In synchronous mode all writes are ordered
104 if disabled bcache will not generally wait for writes to
156 For a cache, sum of all btree writes in human readable units.
Dprocfs-diskstats16 8 - writes completed
17 9 - writes merged
Dsysfs-devices-platform-docg310 writes or both.
25 writes or both.
Dsysfs-class-net-grcan8 and writes the "Enable 0" bit of the configuration register.
20 and writes the "Enable 1" bit of the configuration register.
/Linux-v4.19/Documentation/block/
Dkyber-iosched.txt5 reads and synchronous writes. Kyber will throttle requests in order to meet
14 Target latency for synchronous writes (in nanoseconds).
Ddeadline-iosched.txt30 Similar to read_expire mentioned above, but for writes.
52 don't want to starve writes indefinitely either. So writes_starved controls
53 how many times we give preference to reads over writes. When that has been
54 done writes_starved number of times, we dispatch some writes based on the
/Linux-v4.19/Documentation/md/
Draid5-cache.txt17 In both modes, all writes to the array will hit cache disk first. This means
26 disks and it's possible the writes don't hit all RAID disks yet before the
51 write. For non-full-stripe writes, MD must read old data before the new parity
52 can be calculated. These synchronous reads hurt write throughput. Some writes
88 order in which MD writes data to cache disk and RAID disks. Specifically, in
89 write-through mode, MD calculates parity for IO data, writes both IO data and
90 parity to the log, writes the data and parity to RAID disks after the data and
94 In write-back mode, MD writes IO data to the log and reports IO completion. The
108 they are discarded too. MD then loads valid data and writes them to RAID disks
/Linux-v4.19/tools/memory-model/litmus-tests/
DREADME19 successive writes to the same variable are ordered.
22 Test of independent reads from independent writes with smp_mb()
25 the order of a pair of writes, where each write is to a different
30 Test of independent reads from independent writes with nothing
33 order of a pair of writes, where each write is to a different
53 of two variables then writes to the other?
58 writes to the other?
94 process writes data and then a flag, and the other process reads
DIRIW+poonceonces+OnceOnce.litmus6 * 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
DIRIW+fencembonceonces+OnceOnce.litmus6 * Test of independent reads from independent writes with smp_mb()
9 * of writes, where each write is to a different variable by a different
/Linux-v4.19/Documentation/device-mapper/
Ddelay.txt4 Device-Mapper's "delay" target delays reads and/or writes
26 # splitting reads and writes to different devices $1 $2
Dlog-writes.txt1 dm-log-writes
58 log-writes <dev_path> <log_dev_path>
88 Every log has a mark at the end labeled "dm-log-writes-end".
94 It can be found here: https://github.com/josefbacik/log-writes
102 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
122 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
/Linux-v4.19/Documentation/driver-api/
Ddevice-io.rst76 are burned by the fact that PCI bus writes are posted asynchronously. A
78 writes have occurred in the specific cases the author cares. This kind
107 (e.g. SGI Challenge, Origin and Altix machines) posted writes won't be
109 properly protect parts of your driver that do memory-mapped writes with
114 (not that it's simply ordered with respect to other writes), since a
140 CPU A: mmiowb(); /* ensure no other writes beat us to the device */
152 outstanding DMA writes from that bus, since for some devices the result of
155 next readb() call has no relation to any previous DMA writes
/Linux-v4.19/drivers/md/
Ddm-raid1.c61 struct bio_list writes; member
127 bl = (rw == WRITE) ? &ms->writes : &ms->reads; in queue_bio()
679 static void do_writes(struct mirror_set *ms, struct bio_list *writes) in do_writes() argument
688 if (!writes->head) in do_writes()
699 while ((bio = bio_list_pop(writes))) { in do_writes()
739 bio_list_merge(&ms->writes, &requeue); in do_writes()
854 struct bio_list reads, writes, failures; in do_mirror() local
859 writes = ms->writes; in do_mirror()
862 bio_list_init(&ms->writes); in do_mirror()
869 do_writes(ms, &writes); in do_mirror()
[all …]
/Linux-v4.19/drivers/md/bcache/
Dbtree.h146 struct btree_write writes[2]; member
169 return b->writes + btree_node_write_idx(b); in btree_current_write()
174 return b->writes + (btree_node_write_idx(b) ^ 1); in btree_prev_write()
/Linux-v4.19/Documentation/rapidio/
Dmport_cdev.txt31 - Reads and writes from/to configuration registers of mport devices
33 - Reads and writes from/to configuration registers of remote RapidIO devices.
34 This operations are defined as RapidIO Maintenance reads/writes in RIO spec.
46 port-writes or both (RIO_SET_EVENT_MASK/RIO_GET_EVENT_MASK)
/Linux-v4.19/Documentation/cdrom/
Dpacket-writing.txt42 shall implement "true random writes with 2KB granularity", which means
52 host to perform aligned writes at 32KB boundaries. Other drives do
54 writes are not 32KB aligned.
57 generates aligned writes.
/Linux-v4.19/arch/riscv/include/asm/
Dio.h271 __io_writes_outs(writes, u8, b, __io_bw(), __io_aw())
272 __io_writes_outs(writes, u16, w, __io_bw(), __io_aw())
273 __io_writes_outs(writes, u32, l, __io_bw(), __io_aw())
292 __io_writes_outs(writes, u64, q, __io_bw(), __io_aw())

12345678910>>...13