| /linux/drivers/gpib/ni_usb/ |
| H A D | ni_usb_gpib.c | 520 const struct ni_usb_register *writes, int num_writes, in ni_usb_write_registers() argument
541 i += ni_usb_bulk_register_write(&out_data[i], writes[j]); in ni_usb_write_registers()
1072 struct ni_usb_register writes[4]; in ni_usb_request_system_control() local
1079 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control()
1080 writes[i].address = CMDR; in ni_usb_request_system_control()
1081 writes[i].value = SETSC; in ni_usb_request_system_control()
1083 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control()
1084 writes[i].address = nec7210_to_tnt4882_offset(AUXMR); in ni_usb_request_system_control()
1085 writes[i].value = AUX_CIFC; in ni_usb_request_system_control()
1088 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control()
[all …]
|
| /linux/tools/perf/scripts/perl/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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};
|
| /linux/drivers/gpib/agilent_82357a/ |
| H A D | agilent_82357a.c | 214 const struct agilent_82357a_register_pairlet *writes, in agilent_82357a_write_registers() argument
240 out_data[i++] = writes[j].address; in agilent_82357a_write_registers()
241 out_data[i++] = writes[j].value; in agilent_82357a_write_registers()
764 struct agilent_82357a_register_pairlet writes[2]; in agilent_82357a_request_system_control() local
773 writes[i].address = AUXCR; in agilent_82357a_request_system_control()
775 writes[i].value = AUX_RQC; in agilent_82357a_request_system_control()
781 writes[i].address = HW_CONTROL; in agilent_82357a_request_system_control()
782 writes[i].value = a_priv->hw_control_bits; in agilent_82357a_request_system_control()
784 retval = agilent_82357a_write_registers(a_priv, writes, i); in agilent_82357a_request_system_control()
952 struct agilent_82357a_register_pairlet writes[2]; in agilent_82357a_parallel_poll() local
[all …]
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | atomic_writes.rst | 10 Atomic (untorn) block writes ensure that either the entire write is committed
11 to disk or none of it is. This prevents "torn writes" during power loss or
12 system crashes. The ext4 filesystem supports atomic writes (only with Direct
14 supports hardware atomic writes. This is supported in the following two ways:
24 EXT4 now also supports atomic writes spanning multiple filesystem blocks
32 Basic requirements for atomic writes in ext4:
35 2. The underlying block device must support atomic writes
36 3. For single-fsblock atomic writes:
39 4. For multi-fsblock atomic writes:
45 atomic writes on ext4 are only supported if underlying storage device supports
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | io_ordering.rst | 2 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
|
| H A D | device-io.rst | 76 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 outstanding DMA writes from that bus, since for some devices the result of
110 next readb() call has no relation to any previous DMA writes
176 Note that posted writes are not strictly ordered against a spinlock, see
305 * Uncached - CPU-side caches are bypassed, and all reads and writes are handled
313 * No repetition - The CPU may not issue multiple reads or writes for a single
316 being issued to the device, and multiple writes are not combined into larger
317 writes. This may or may not be enforced when using __raw I/O accessors or
323 On many platforms and buses (e.g. PCI), writes issued through ioremap()
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-block-bcache | 55 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
149 For a cache, sum of all btree writes in human readable units.
|
| H A D | debugfs-msi-wmi-platform | 9 at file offset 0. Partial writes or writes at a different offset are not
|
| H A D | procfs-diskstats | 17 8 writes completed
18 9 writes merged
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse-io.rst | 17 In direct-io mode the page cache is completely bypassed for reads and writes.
23 after any writes to the file. All mmap modes are supported.
25 The cached mode has two sub modes controlling how writes are handled. The
32 uncached, but fully written pages). No READ requests are ever sent for writes,
35 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
|
| /linux/Documentation/admin-guide/ |
| H A D | iostats.rst | 45 Field 2 -- # of reads merged, field 6 -- # of writes merged (unsigned long)
46 Reads and writes which are adjacent to each other may be merged for
58 Field 5 -- # of writes completed (unsigned long)
59 This is the total number of writes completed successfully.
61 Field 6 -- # of writes merged (unsigned long)
68 This is the total number of milliseconds spent by all writes (as
145 Field 3 -- # of writes issued
146 This is the total number of writes issued to this partition.
160 reads/writes before merges for partitions and after for disks. Since a
162 the number of reads/writes issued can be several times higher than the
[all …]
|
| /linux/Documentation/driver-api/md/ |
| H A D | raid5-cache.rst | 19 In both modes, all writes to the array will hit cache disk first. This means
28 disks and it's possible the writes don't hit all RAID disks yet before the
53 write. For non-full-stripe writes, MD must read old data before the new parity
54 can be calculated. These synchronous reads hurt write throughput. Some writes
90 order in which MD writes data to cache disk and RAID disks. Specifically, in
91 write-through mode, MD calculates parity for IO data, writes both IO data and
92 parity to the log, writes the data and parity to RAID disks after the data and
96 In write-back mode, MD writes IO data to the log and reports IO completion. The
110 they are discarded too. MD then loads valid data and writes them to RAID disks
|
| /linux/arch/riscv/include/asm/ |
| H A D | io.h | 112 __io_writes_outs(writes, u8, b, __io_bw(), __io_aw())
113 __io_writes_outs(writes, u16, w, __io_bw(), __io_aw())
114 __io_writes_outs(writes, u32, l, __io_bw(), __io_aw())
133 __io_writes_outs(writes, u64, q, __io_bw(), __io_aw())
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | delay.rst | 5 Device-Mapper's "delay" target delays reads and/or writes
43 # splitting reads to device $1 but writes and flushes to different device $2
51 # Create mapped device delaying reads for 50ms, writes for 100ms and flushes for 333ms
|
| H A D | writecache.rst | 5 The writecache target caches writes on persistent memory or on SSD. It
37 when the application writes this amount of blocks without
58 new writes (however, writes to already cached blocks are
60 writes) and it will gradually writeback any cached
|
| H A D | log-writes.rst | 2 dm-log-writes
59 log-writes <dev_path> <log_dev_path>
93 Every log has a mark at the end labeled "dm-log-writes-end".
99 It can be found here: https://github.com/josefbacik/log-writes
107 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
127 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
|
| /linux/lib/ |
| H A D | Kconfig.kcsan | 195 particular reordered writes.
210 bool "Assume that plain aligned writes up to word size are atomic"
214 Assume that plain aligned writes up to word size are atomic by
218 writes up to word size: conflicts between marked reads and plain
219 aligned writes up to word size will not be reported as data races;
220 notice that data races between two conflicting plain aligned writes
229 writes will never be reported as a data race, however, will cause
230 plain reads and marked writes to result in "unknown origin" reports.
236 accesses, conflicting marked atomic reads and plain writes will not
238 due to two conflicting plain writes will be reported (aligned and
|
| /linux/Documentation/block/ |
| H A D | kyber-iosched.rst | 6 reads and synchronous writes. Kyber will throttle requests in order to meet
15 Target latency for synchronous writes (in nanoseconds).
|
| H A D | deadline-iosched.rst | 29 Similar to read_expire mentioned above, but for writes.
51 don't want to starve writes indefinitely either. So writes_starved controls
52 how many times we give preference to reads over writes. When that has been
53 done writes_starved number of times, we dispatch some writes based on the
|
| /linux/tools/memory-model/litmus-tests/ |
| H A 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?
104 process writes data and then a flag, and the other process reads
182 For example, if the one process writes to a pair of variables, and
|
| H A 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
|
| H 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
|
| /linux/drivers/md/ |
| H A D | dm-raid1.c | 66 struct bio_list writes; member
132 bl = (rw == WRITE) ? &ms->writes : &ms->reads; in queue_bio()
686 static void do_writes(struct mirror_set *ms, struct bio_list *writes) in do_writes() argument
695 if (!writes->head) in do_writes()
706 while ((bio = bio_list_pop(writes))) { in do_writes()
746 bio_list_merge(&ms->writes, &requeue); in do_writes()
863 struct bio_list reads, writes, failures; in do_mirror() local
868 writes = ms->writes; in do_mirror()
871 bio_list_init(&ms->writes); in do_mirror()
878 do_writes(ms, &writes); in do_mirror()
[all …]
|