Home
last modified time | relevance | path

Searched refs:writes (Results 1 – 200 of 243) sorted by relevance

12

/linux-4.1.27/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-4.1.27/Documentation/
Dio_ordering.txt2 platforms, driver writers are responsible for ensuring that I/O writes to
5 chipset to flush pending writes to the device before any reads are posted. A
8 subsequent writes to I/O space arrived only after all prior writes (much like a
46 pending writes before actually posting the read to the chipset, preventing
Diostats.txt62 Field 2 -- # of reads merged, field 6 -- # of writes merged
63 Reads and writes which are adjacent to each other may be merged for
72 Field 5 -- # of writes completed
73 This is the total number of writes completed successfully.
74 Field 6 -- # of writes merged
79 This is the total number of milliseconds spent by all writes (as
123 Field 3 -- # of writes issued
124 This is the total number of writes issued to this partition.
137 reads/writes before merges for partitions and after for disks. Since a
139 the number of reads/writes issued can be several times higher than the
[all …]
Dbcache.txt12 designed to avoid random writes at all costs; it fills up an erase block
19 writes as completed until they're on stable storage).
21 Writeback caching can use most of the cache for buffering writes - writing
118 - For writethrough writes, if the write to the cache errors we just switch to
122 - For writeback writes, we currently pass that error back up to the
177 The default is 2000 us (2 milliseconds) for reads, and 20000 for writes.
193 Solution: warm the cache by doing writes, or use the testing branch (there's
287 Amount of IO (both reads and writes) that has bypassed the cache
353 Journal writes will delay for up to this many milliseconds, unless a cache
405 Minimum granularity of writes - should match hardware sector size.
[all …]
DDMA-attributes.txt12 all pending DMA writes to complete, and thus provides a mechanism to
28 DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
29 may be weakly ordered, that is that reads and writes may pass each other.
38 DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
Dlocal_ops.txt9 those local variables across CPUs when the order of memory writes matters.
32 CPU writes to the local_t data. This is done by using per cpu data and making
35 out of order wrt other memory writes by the owner CPU.
106 relatively to other memory writes happening on the CPU that owns the data.
Dramoops.txt10 Ramoops is an oops/panic logger that writes its logs to RAM before the system
32 power of two) and each oops/panic writes a "record_size" chunk of
Dmd.txt283 clean - no pending writes, but otherwise active.
288 If written to an active array that has pending writes, then fails.
294 clean, but writes are blocked waiting for 'active' to be written.
297 like active, but no writes have been seen for a while (safe_mode_delay).
323 writes. If there are more than this, new writes will by
391 Writing "-blocked" clears the "blocked" flags and allows writes
613 writes are complete. Valid values are 0 to stripe_cache_size.
Dmd-cluster.txt7 The bitmaps record all writes that may have been started on that node,
18 node writes to any given block at a time, so a write
Dcircular-buffers.txt131 [3] To a third party, the order in which the writes to the indices by the
223 before it writes the new tail pointer, which will erase the item.
Dnommu-mmap.txt55 - Writes to the file do not affect the mapping; writes to the mapping
63 on writes to the file underneath that page no longer get reflected into
72 pages written back to file; writes to file reflected into pages backing
Dxillybus.txt206 host pipe (the FPGA "writes").
272 FPGA, the Xillybus IP core writes it to one of the DMA buffers. When the
276 the character device. When all data has been read, the host writes on the
Dcachetlb.txt281 Any time the kernel writes to a page cache page, _OR_
292 The phrase "kernel writes to a page cache page" means,
Dthis_cpu_ops.txt325 Even in cases where the remote writes are rare, please bear in
Doops-tracing.txt23 handed to syslogd which writes it to a syslog file, typically
Dvme_api.txt162 In addition to simple reads and writes, a function is provided to do a
/linux-4.1.27/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-diskstats15 8 - writes completed
16 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.
Dsysfs-class-mei23 The ME FW writes its status information into fw status
Dsysfs-gpio20 /value ... always readable, writes fail for input GPIOs
Dsysfs-firmware-gsmi53 clearing though, and this writes to this file
Dsysfs-block-zram37 writes (failed or successful) done on this device.
58 failed writes happened on this device.
Dsysfs-wusb_cbaf16 3. The CM writes the host name, supported band groups,
Dsysfs-block11 5 - writes completed
12 6 - writes merged
Dsysfs-devices-system-cpu48 probe: writes to this file will dynamically add a CPU to the
52 release: writes to this file dynamically remove a CPU from
Dsysfs-power200 writes "off" to /sys/power/autosleep.
/linux-4.1.27/Documentation/device-mapper/
Ddelay.txt4 Device-Mapper's "delay" target delays reads and/or writes
24 # 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"
Ddm-flakey.txt13 which can delay reads and writes and/or send them to different
42 <direction>: Either 'r' to corrupt reads or 'w' to corrupt writes.
Ddm-log.txt9 are writing to it because the writes need to be replicated for all
11 Once all writes are complete, the region is considered clean again.
Ddm-crypt.txt72 Disable offloading writes to a separate thread after encryption.
76 thread because it benefits CFQ to have writes submitted using the
Dzero.txt5 zero'd data on reads and silently drops writes. This is similar behavior to
Dstatistics.txt120 5. the number of writes completed
121 6. the number of writes merged
Dcache.txt87 the origin device (all reads miss the cache) and all writes are
92 the cache will gradually cool as writes take place. If the coherency of
130 cache. If power is lost you may lose some recent writes. The metadata
205 underlying storage). Reads and writes always go to
Dera.txt89 The target uses a bitset to record writes in the current era. It also
Dpersistent-data.txt48 ensures that all data is flushed before it writes the superblock.
Dcache-policies.txt79 The cleaner writes back all dirty blocks in a cache to decommission it.
/linux-4.1.27/drivers/md/
Ddm-delay.c36 unsigned writes; member
91 delayed->context->writes--; in flush_delayed_bios()
144 dc->reads = dc->writes = 0; in delay_ctr()
244 dc->writes++; in delay_bio()
301 DMEMIT("%u %u", dc->reads, dc->writes); in delay_status()
Ddm-raid1.c57 struct bio_list writes; member
125 bl = (rw == WRITE) ? &ms->writes : &ms->reads; in queue_bio()
666 static void do_writes(struct mirror_set *ms, struct bio_list *writes) in do_writes() argument
675 if (!writes->head) in do_writes()
686 while ((bio = bio_list_pop(writes))) { in do_writes()
726 bio_list_merge(&ms->writes, &requeue); in do_writes()
836 struct bio_list reads, writes, failures; in do_mirror() local
841 writes = ms->writes; in do_mirror()
844 bio_list_init(&ms->writes); in do_mirror()
851 do_writes(ms, &writes); in do_mirror()
[all …]
DKconfig240 delayed writes.
305 reads over writes.
312 A simple cache policy that writes back all data to the
374 A target that discards writes, and returns all zeroes for
411 A target that delays reads and/or writes and can send
463 tristate "Log writes target support"
474 be called dm-log-writes.
DMakefile59 obj-$(CONFIG_DM_LOG_WRITES) += dm-log-writes.o
/linux-4.1.27/Documentation/block/
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
Dcfq-iosched.txt250 All async writes go on async service tree. There is no idling on async
290 more writes to be dispatched from same context soon, should be able
291 to specify REQ_NOIDLE on writes and that probably should work well for
Dqueue-sysfs.txt89 this amount, since it applies only to reads or writes (not the accumulated
/linux-4.1.27/Documentation/filesystems/
Ddax.txt7 The page cache is usually used to buffer reads and writes to files.
13 extra copy by performing reads and writes directly to the storage device.
66 - ensuring that there is sufficient locking between reads, writes,
91 reads/writes to those memory ranges from a non-DAX file will fail (note
92 that O_DIRECT reads/writes _of a DAX file_ do work, it is the memory
Dudf.txt11 dvd+rw drives and media support true random sector writes, and so a udf
16 and read-modify-write cycles to allow the filesystem random sector writes
17 while providing the hardware with only full packet writes. While not
Docfs2.txt96 coherency=full (*) Disallow concurrent O_DIRECT writes, cluster inode
99 for O_DIRECT writes.
100 coherency=buffered Allow concurrent O_DIRECT writes without EX lock among
Dgfs2.txt8 iSCSI, NBD, etc). GFS reads and writes to the block device like a local
Dceph.txt97 maximum. Ceph will normally size writes based on the file stripe
118 Disable CRC32C calculation for data writes. If set, the storage node
Dqnx6.txt156 qnx6fs deals with writes.
158 always uses blocks from the lower half whilst superblock #2 just writes to
Df2fs.txt34 "A log-structured file system writes all modifications to disk sequentially in
58 Since LFS is based on out-of-place writes, it produces so many obsolete blocks
139 data writes.
432 leaf data writes.
546 from random writes, but no cleaning process is needed. F2FS adopts a hybrid
Dbtrfs.txt52 Auto defragmentation detects small random writes into files and queue
169 Enable/disable the tree logging used for fsync and O_SYNC writes.
Dgfs2-uevents.txt95 With recent versions of gfs2-utils, mkfs.gfs2 writes a UUID
Dlogfs.txt33 writes happen from front (low addresses) to back (high addresses. If
160 The GC code also checks for aliases and writes then back if their
Drelay.txt286 used - writes from any cpu will transparently end up in the global
289 writes in a spinlock, or by copying a write function from relay.h and
318 In 'overwrite' mode, also known as 'flight recorder' mode, writes
321 been consumed. In no-overwrite mode, writes will fail, i.e. data will
Dsysfs-pci.txt59 The read only files are informational, writes to them will be ignored, with
Dxfs-self-describing-metadata.txt23 manual task of verifying that things like single bit errors or misplaced writes
96 mis-directed writes - a write might be misdirected to the wrong LUN and so be
116 looking at. The owner information can also identify misplaced writes (e.g.
Dspufs.txt98 block until the SPU writes to its interrupt mailbox channel.
189 buffer. Subsequent writes to the same file descriptor overwrite
258 buffer. Subsequent writes to the same file descriptor overwrite
Dubifs.txt54 which makes UBIFS much faster on writes.
Dhpfs.txt182 correctly and writes warning if it finds them. If you see this message, this is
199 marks them as short (and writes "minor fs error corrected"). This bug is not in
Dext3.txt20 used to prevent writes to the filesystem.
Daffs.txt199 than 1 process writes to a (small) diskette, the blocks are allocated
Dmandatory-locking.txt108 mandatory locks, so reads and writes to locked files always block when they
Dext4.txt135 writes to the filesystem.
267 writes out the block(s) in question. This
Dxfs.txt57 writes into the journal and for data integrity operations.
/linux-4.1.27/drivers/md/bcache/
Dbtree.h145 struct btree_write writes[2]; member
168 return b->writes + btree_node_write_idx(b); in btree_current_write()
173 return b->writes + (btree_node_write_idx(b) ^ 1); in btree_prev_write()
Dbtree.c1513 struct closure *writes, struct gc_stat *gc) in btree_gc_recurse() argument
1556 ret = btree_gc_recurse(last->b, op, writes, gc); in btree_gc_recurse()
1569 bch_btree_node_write(last->b, writes); in btree_gc_recurse()
1587 bch_btree_node_write(i->b, writes); in btree_gc_recurse()
1596 struct closure *writes, struct gc_stat *gc) in bch_btree_gc_root() argument
1620 ret = btree_gc_recurse(b, op, writes, gc); in bch_btree_gc_root()
1729 struct closure writes; in bch_btree_gc() local
1736 closure_init_stack(&writes); in bch_btree_gc()
1742 ret = btree_root(gc_root, c, &op, &writes, &stats); in bch_btree_gc()
1743 closure_sync(&writes); in bch_btree_gc()
/linux-4.1.27/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-4.1.27/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt30 or down by additional writes to nfsd/threads or by writes to
Dnfs.txt85 writes the result into the rpc_pipefs pseudo-file
/linux-4.1.27/fs/jffs2/
DTODO4 space it could take. Let GC flush the outstanding writes because the
23 - Split writes so they go to two separate blocks rather than just c->nextblock.
/linux-4.1.27/block/
Ddeadline-iosched.c247 const int writes = !list_empty(&dd->fifo_list[WRITE]); in deadline_dispatch_requests() local
271 if (writes && (dd->starved++ >= dd->writes_starved)) in deadline_dispatch_requests()
283 if (writes) { in deadline_dispatch_requests()
/linux-4.1.27/arch/parisc/
DKconfig.debug10 in order to catch accidental (and incorrect) writes to such const
/linux-4.1.27/drivers/ntb/
DKconfig7 connecting 2 systems. When configured, writes to the device's PCI
/linux-4.1.27/drivers/s390/block/
DKconfig87 prompt "SCM force cluster writes"
90 Force writes to Storage Class Memory (SCM) to be in done in clusters.
/linux-4.1.27/Documentation/trace/
Dring-buffer-design.txt17 tail - where new writes happen in the ring buffer.
21 producer - the task that writes into the ring buffer (same as writer)
284 and will not be a full commit until all writes have been committed.
292 page then no more writes may take place (regardless of the mode
457 and writes only preempt in "stack" formation.
567 and more writes take place, the head page must be moved forward before the
628 As stated before, if enough writes preempt the first write, the
630 page. At this time, we must start dropping writes (usually with some kind
659 tail page wrapped the buffer, and we must drop new writes.
671 Nested writes
[all …]
Dmmiotrace.txt150 For instance, the following awk filter will pass all 32-bit writes that target
162 - replaying MMIO logs, i.e., re-executing the recorded writes
Devents-kmem.txt90 line bounces due to writes between CPUs and worth investigating if pages
/linux-4.1.27/Documentation/devicetree/bindings/
Deeprom.txt20 - read-only: this parameterless property disables writes to the eeprom
/linux-4.1.27/Documentation/s390/
Ds390dbf.txt28 An event-call writes the specified debug entry to the active debug
34 An exception-call writes the specified debug entry to the log and
191 Description: writes debug entry to active debug area (if level <= actual
206 Description: writes debug entry to active debug area (if level <= actual
219 Description: writes debug entry in ascii format to active debug area
233 Description: writes debug entry with format string and varargs (longs) to
249 Description: writes debug entry to active debug area (if level <= actual
264 Description: writes debug entry to active debug area (if level <= actual
277 Description: writes debug entry in ascii format to active debug area
292 Description: writes debug entry with format string and varargs (longs) to
Dzfcpdump.txt44 reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
47 initramfs with a user space application that writes the dump to a SCSI
D3270.txt187 driver writes terminal output to it, starting at the top line and going
/linux-4.1.27/Documentation/devicetree/bindings/misc/
Dat25.txt14 - read-only : this parameter-less property disables writes to the eeprom
/linux-4.1.27/lib/xz/
DKconfig54 data and writes diagnostics to the system log.
/linux-4.1.27/arch/mips/sgi-ip27/
DTODO1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay
/linux-4.1.27/drivers/gpu/drm/msm/
DKconfig35 Compile in support for logging register reads/writes in a format
DNOTES85 parse logged register reads/writes (both from downstream android fbdev
/linux-4.1.27/Documentation/w1/masters/
Dds249052 should match reads and writes as well as data sizes. Reads and
53 writes are serialized and the status verifies that the chip is idle
/linux-4.1.27/arch/mn10300/mm/
DKconfig.cache11 Write-Back caching mode involves the all reads and writes causing
27 flushed if writes are made that subsequently need to be executed or
/linux-4.1.27/Documentation/scsi/
Dst.txt49 users (buffered and asynchronous writes). The modes also allow choices
83 By default the driver writes one filemark when the device is closed after
188 NOTE that if direct i/o is used, the small writes are not buffered. This may
189 cause a surprise when moving from 2.4. There small writes (e.g., tar without
196 at the next tape operation. Asynchronous writes are not done with
199 Buffered writes and asynchronous writes may in some rare cases cause
370 MT_ST_ASYNC_WRITES asynchronous writes (mode)
375 MT_ST_DEF_WRITES the defaults are meant only for writes (mode)
498 When using read ahead or buffered writes the position within the file
521 ps), ps writes the function name in the WCHAN field. If not, you have
Dscsi-changer.txt21 and one for the device which actually reads and writes the data. The
38 data transfer - this is the device which reads/writes, i.e. the
Din2000.txt83 inline code for IO writes. Made a few other changes and
/linux-4.1.27/Documentation/i2c/
Dsmbus-protocol115 This writes a single byte to a device, to a designated register. The
136 available for writes where the two data bytes are the other way
168 The opposite of the Block Read command, this writes up to 32 bytes to
266 The opposite of the Block Read command, this writes bytes to
Dfault-codes52 may have a way to report PEC mismatches on writes from the
Dslave-interface173 on writes an action should be immediately triggered. For reads, the data in
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds28e0425 A write operation on the "eeprom" file writes the given byte sequence
/linux-4.1.27/Documentation/arm/
D00-INDEX52 - Voting locks, low-level mechanism relying on memory system atomic writes.
Dvlocks.txt15 writes to a single memory location. To arbitrate, every CPU "votes for
/linux-4.1.27/arch/metag/kernel/
Dhead.S53 ! In case GCOn has just been turned on we need to fence any writes that
/linux-4.1.27/fs/gfs2/
DKconfig12 and writes to the block device like a local filesystem, but also uses
/linux-4.1.27/Documentation/hwmon/
Dlm7735 read-only. Setting temp1_crit_hyst writes the difference between
Demc140356 are read-only. Setting temp1_crit_hyst writes the difference between
Dlm90267 usage (+33% for writes, +25% for reads) in normal conditions. With the need
Dsysfs-interface66 "sysfs attribute writes interpretation" section at the end of this file.
711 sysfs attribute writes interpretation
Dpmbus-core91 - READ commands are read-only; writes are either ignored or return an error.
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-block-zram14 writes (failed or successful) done on this device.
38 failed writes happened on this device.
/linux-4.1.27/Documentation/misc-devices/
Dad525x_dpot.txt43 You can use simple reads/writes to access these files:
Dmax687561 Reads and writes are performed differently depending on the address range.
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dgpio-control-nand.txt25 GPIO state and before and after command byte writes, this register will be
Dgpmc-nor.txt16 - gpmc,cs-wr-off-ns: Chip-select de-assertion time for writes
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dti-gpmc.txt108 - gpmc,sync-write Enables synchronous writes. Defaults to asynchronous
113 - gpmc,wait-on-write Enables wait monitoring on writes.
/linux-4.1.27/drivers/scsi/arm/
Dacornscsi.h309 unsigned int writes; member
Dfas216.h262 unsigned int writes; member
Dfas216.c208 info->stats.reads, info->stats.writes, info->stats.miscs, in fas216_dumpinfo()
1831 info->stats.writes += 1; in fas216_allocate_tag()
2983 info->stats.writes, info->stats.miscs, in fas216_print_stats()
/linux-4.1.27/drivers/staging/fwserial/
Dfwserial.h171 unsigned writes[DISTRIBUTION_MAX_INDEX + 1]; member
Dfwserial.c163 sum += stats->writes[j]; in fwtty_dump_profile()
166 seq_printf(m, "%6d", stats->writes[j]); in fwtty_dump_profile()
1113 fwtty_profile_data(port->stats.writes, c); in fwtty_write()
/linux-4.1.27/drivers/block/drbd/
Ddrbd_req.c1167 list_add_tail(&req->tl_requests, &device->submit.writes); in drbd_queue_write()
1404 list_splice_tail_init(&device->submit.writes, &incoming); in do_submit()
1444 list_splice_tail_init(&device->submit.writes, &incoming); in do_submit()
1472 if (list_empty(&device->submit.writes)) in do_submit()
1476 list_splice_tail_init(&device->submit.writes, &more_incoming); in do_submit()
DKconfig29 simply writes the data to its lower level block device.
Ddrbd_main.c2220 struct list_head writes; member
2226 LIST_HEAD(writes); in do_retry()
2230 list_splice_init(&retry->writes, &writes); in do_retry()
2233 list_for_each_entry_safe(req, tmp, &writes, tl_requests) { in do_retry()
2281 list_move_tail(&req->tl_requests, &retry.writes); in drbd_restart_request()
2711 INIT_LIST_HEAD(&device->submit.writes); in init_submitter()
2954 INIT_LIST_HEAD(&retry.writes); in drbd_init()
/linux-4.1.27/Documentation/cgroups/
Dcpuacct.txt47 against concurrent writes.
Dblkio-controller.txt93 Limits for writes can be put using blkio.throttle.write_bps_device file.
392 - Currently only sync IO queues are support. All the buffered writes are
394 differentiation between buffered writes between groups.
/linux-4.1.27/Documentation/vm/
Dsoft-dirty.txt4 writes to. In order to do this tracking one should
Dzswap.txt23     drastically reducing life-shortening writes.
Dslub.txt221 writes after the object. All bytes should always have the same
231 at least 4 bytes of padding. This allows the detection of writes
Dfrontswap.txt43 in swap device writes is lost (and also a non-trivial performance advantage)
254 swap subsystem then writes the new data to the read swap device,
/linux-4.1.27/Documentation/i2c/busses/
Di2c-sis96x52 * The driver does not support SMBus block reads/writes; I may add them if a
/linux-4.1.27/drivers/mtd/onenand/
DKconfig13 bool "Verify OneNAND page writes"
/linux-4.1.27/drivers/mmc/card/
DKconfig63 Development driver that performs a series of reads and writes
/linux-4.1.27/Documentation/blockdev/
Dzram.txt113 num_write RO the number of writes
114 failed_writes RO the number of failed writes
/linux-4.1.27/drivers/scsi/
Deata_generic.h345 __u32 writes[13]; member
/linux-4.1.27/Documentation/rapidio/
Dtsi721.txt8 doorbells, inbound maintenance port-writes and RapidIO messaging.
Dsysfs.txt49 config - reads from and writes to the device configuration registers.
/linux-4.1.27/Documentation/video4linux/
Dcpia2_overview.txt35 of contiguous registers. Random mode reads or writes random registers with
/linux-4.1.27/arch/metag/
DKconfig128 reordering of writes from different hardware threads when SMP is
130 attempt to catch some of the cases, and also before writes to shared
/linux-4.1.27/Documentation/fb/
Dsstfb.txt98 reads and writes are discarded.
108 slowpci=1 fastpci Enable or disable fast PCI read/writes.
Ddeferred_io.txt25 writes to occur at minimum cost. Then after some time when hopefully things
/linux-4.1.27/Documentation/fmc/
Dfmc-chardev.txt51 repeated reading data is written to stdout; repeated writes read from
Dfmc-write-eeprom.txt43 This is a real example: that writes 5 bytes at position 0x110:
/linux-4.1.27/fs/btrfs/
DKconfig49 writes of the super block). The goal is to verify that the
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt14 The guest writes a selector value (a key) to the selector register, and then
/linux-4.1.27/Documentation/networking/
Dtuntap.txt17 writes them to the user space program.
211 and decrypts the data received and writes the packet to the TAP device,
De1000e.txt239 NOTE: The machine must be power cycled (full off/on) when enabling NVM writes
/linux-4.1.27/drivers/staging/vme/devices/
Dvme_user.c109 unsigned long writes; member
176 statistics.writes = 0; in reset_counters()
/linux-4.1.27/tools/perf/Documentation/
Dperf-timechart.txt29 Lower bar shows outgoing events (disk writes, egress network packets).
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dgpmc-eth.txt31 - gpmc,cs-wr-off-ns: Chip-select de-assertion time for writes
/linux-4.1.27/Documentation/mmc/
Dmmc-async-req.txt24 performance gain is 5% for large writes and 10% on large reads on a L2 cache
/linux-4.1.27/arch/avr32/include/asm/
Dio.h177 static inline void writes##bwl(volatile void __iomem *addr, \ in BUILDIO_MEM()
/linux-4.1.27/drivers/w1/slaves/
DKconfig79 Full block writes are only allowed if the CRC is valid.
/linux-4.1.27/arch/arm/mach-shmobile/include/mach/
Dhead-kzm9g.txt344 LIST "upstream u-boot writes to SDMRA1A for both SBSC 1 and 2, which does"
397 LIST "Magic to avoid hangs and corruption on DRAM writes."
/linux-4.1.27/arch/blackfin/
DKconfig.debug90 bool "Catch NULL pointer reads/writes"
93 Say Y here to catch reads/writes to anywhere in the memory range
/linux-4.1.27/Documentation/RCU/
DNMI-RCU.txt70 writes, the rcu_assign_pointer() ensures that the NMI handler sees the
/linux-4.1.27/Documentation/filesystems/cifs/
DTODO100 there are some easy changes that can be done to parallelize sequential writes,
DCHANGES98 high stress workloads (and the number of retries on socket writes
108 on EAGAIN from the socket too quickly on large writes).
118 lanman and plain text though). Fix writes to be at correct offset when
303 Defer close of a file handle slightly if pending writes depend on that handle
305 stress on writes). Modify cifs Kconfig options to expose CONFIG_CIFS_STATS2
654 Fix unload_nls oops in a mount failure path. Serialize writes to same socket
/linux-4.1.27/lib/
DKconfig.kgdb88 0x0004 - allow arbitrary writes to memory
/linux-4.1.27/Documentation/phy/
Dsamsung-usb2.txt12 registers of the PHY. In some rare cases the order of register writes or
/linux-4.1.27/arch/arm/mach-omap2/
Dsram34xx.S160 dsb @ flush buffered writes to interconnect
/linux-4.1.27/arch/mips/include/asm/
Dio.h488 static inline void writes##bwlq(volatile void __iomem *mem, \ in BUILDIO_MEM()
/linux-4.1.27/arch/sh/include/asm/
Dio.h91 pfx##writes##bwlq(volatile void __iomem *mem, const void *addr, \
/linux-4.1.27/Documentation/sysctl/
Dvm.txt144 Contains the amount of dirty memory at which a process generating disk writes
171 generating disk writes will itself start writing out dirty data.
716 the high water marks for each per cpu page list. If the user writes '0' to this
789 2 = Zone reclaim writes dirty pages out
807 since it cannot use all of system memory to buffer the outgoing writes
Dkernel.txt799 written, and multiple writes on the same sysctl file descriptor
802 perform writes to a sysctl file descriptor when the file position
804 1 - Respect file position when writing sysctl strings. Multiple writes
Dfs.txt154 with writes enabled, any UID or GID that would exceed 65535 is translated
/linux-4.1.27/drivers/net/wireless/b43/
Dradio_2055.c1303 unsigned int i, writes = 0; in b2055_upload_inittab() local
1316 if (++writes % 4 == 0) in b2055_upload_inittab()
/linux-4.1.27/arch/sh/lib64/
Dmemcpy.S20 ! writes.
Dcopy_user_memcpy.S18 ! writes.
/linux-4.1.27/Documentation/x86/
Dpat.txt121 Over time writes to /proc/mtrr will be deprecated in favor of using PAT based
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Ddscr.txt11 configuration register for writes. These configuration register may be used to
/linux-4.1.27/Documentation/filesystems/caching/
Doperations.txt113 This is, for example, used by FS-Cache to handle background writes of
Dfscache.txt394 W Show objects that have pending writes
395 w Show objects that don't have pending writes
Dbackend-api.txt210 writes to be made. FS-Cache itself enqueues this operation and invokes
667 (2) that writes may now proceed against this object.
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt70 will block all writes (either to the card from the system, or
315 Ext3fs seems to be tolerant, retrying reads/writes until it does
/linux-4.1.27/drivers/net/wireless/libertas/
DREADME102 echo "p1 p2 p3 p4 p5 p6" > sleepparams: writes the sleepclock configuration.
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt38 or destination, can group the reads or writes in memory into a buffer,
42 reads/writes it's allowed to do without the controller splitting the
/linux-4.1.27/drivers/mtd/nand/
DKconfig259 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
276 Even if you leave this disabled, you can enable BBT writes at module
/linux-4.1.27/arch/frv/
DKconfig162 Write-Back caching mode involves the all reads and writes causing
/linux-4.1.27/Documentation/isdn/
DsyncPPP.FAQ94 writes in the debug log something like:
/linux-4.1.27/drivers/mtd/devices/
DKconfig62 bool "Verify DataFlash page writes"
/linux-4.1.27/Documentation/sound/alsa/
Dhdspm.txt69 where DMA reads/writes. Since of the bulk mode of PCI it is only
/linux-4.1.27/Documentation/crypto/
Dasync-tx-api.txt66 writes to memory
/linux-4.1.27/Documentation/ia64/
Daliasing.txt21 like UC is, but writes may be delayed and combined to increase
/linux-4.1.27/Documentation/usb/
Dgadget_configfs.txt319 Whenever a user reads/writes the "sa" file, a function is called
Dmass-storage.txt105 default. All the writes to the media are synchronous, which is
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt119 all writes are ignored.
175 >>> a value of 0xff on read, and writes will be dropped. If more than
DMSI-HOWTO.txt42 When a device writes data to memory, then raises a pin-based interrupt,
50 pass the data writes, so by the time the interrupt is raised, the driver
/linux-4.1.27/mm/
DKconfig303 # We also use the bounce pool to provide stable page writes for jbd. jbd
543 soft-dirty bit on pte-s. This bit it set when someone writes
/linux-4.1.27/arch/x86/
DKconfig.debug95 in order to catch accidental (and incorrect) writes to such const
/linux-4.1.27/Documentation/hid/
Duhid.txt86 writes are always handled immediately in a non-blocking fashion. Future requests
/linux-4.1.27/arch/powerpc/
DKconfig.debug80 nothing will appear on the screen (xmon writes directly to the
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dgpc.fuc27 * - bracket certain functions with scratch writes, useful for debugging
/linux-4.1.27/arch/m68k/
DKconfig.cpu378 Copyback caching means that memory writes will be held in an on-chip
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt22 - dirty tracking: report writes to guest memory to enable live migration
93 - writes to control registers (especially cr3)
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-tape.1995-200281 * writes). When using the pipelined mode, the
/linux-4.1.27/Documentation/serial/
Dtty.txt201 TTY_NO_WRITE_SPLIT Prevent driver from splitting up writes into
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dentry.S359 ;; We only need to do this for writes.
/linux-4.1.27/arch/arm/mm/
DKconfig940 this prevents it from merging any further writes. The workaround
951 writes to be retained when the memory system is idle, leading
/linux-4.1.27/drivers/net/
DKconfig232 via physical media writes them to the user space program.
/linux-4.1.27/arch/sparc/
DKconfig368 via writes to /proc/led

12