Searched full:writes (Results 1 – 25 of 256) sorted by relevance
1234567891011
| /Documentation/filesystems/ |
| D | fuse-io.txt | 11 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
|
| D | dax.txt | 7 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.
69 - ensuring that there is sufficient locking between reads, writes,
128 how to do this). In the non struct page cases O_DIRECT reads/writes to
130 reads/writes _of a DAX file_ do work, it is the memory that is being
|
| D | udf.txt | 9 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
|
| D | ocfs2.txt | 96 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
|
| /Documentation/ |
| D | io_ordering.txt | 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
|
| /Documentation/ABI/testing/ |
| 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
156 For a cache, sum of all btree writes in human readable units.
|
| D | procfs-diskstats | 16 8 - writes completed
17 9 - writes merged
|
| D | sysfs-devices-platform-docg3 | 10 writes or both.
25 writes or both.
|
| D | sysfs-class-net-grcan | 8 and writes the "Enable 0" bit of the configuration register.
20 and writes the "Enable 1" bit of the configuration register.
|
| D | sysfs-class-mei | 23 The ME FW writes its status information into fw status
55 Set maximal number of pending writes
|
| /Documentation/driver-api/md/ |
| 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
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 67 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
155 Field 3 -- # of writes issued
156 This is the total number of writes issued to this partition.
170 reads/writes before merges for partitions and after for disks. Since a
172 the number of reads/writes issued can be several times higher than the
[all …]
|
| D | bcache.rst | 17 designed to avoid random writes at all costs; it fills up an erase block
24 writes as completed until they're on stable storage).
26 Writeback caching can use most of the cache for buffering writes - writing
131 - For writethrough writes, if the write to the cache errors we just switch to
135 - For writeback writes, we currently pass that error back up to the
376 The default is 2000 us (2 milliseconds) for reads, and 20000 for writes.
392 Solution: warm the cache by doing writes, or use the testing branch (there's
489 Amount of IO (both reads and writes) that has bypassed the cache
552 Journal writes will delay for up to this many milliseconds, unless a cache
606 Minimum granularity of writes - should match hardware sector size.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 2 dm-log-writes
24 the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only
25 completed WRITEs, at the time the REQ_PREFLUSH is issued, are added in order to
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"
|
| D | delay.rst | 5 Device-Mapper's "delay" target delays reads and/or writes
30 # splitting reads and writes to different devices $1 $2
|
| D | dm-flakey.rst | 14 which can delay reads and writes and/or send them to different
58 Either 'r' to corrupt reads or 'w' to corrupt writes.
|
| D | dm-zoned.rst | 11 device-side performance degradation due to excessive random writes on
49 zones of the device may be used also for buffering user random writes.
52 reused for buffering incoming random writes.
103 unaligned writes to unbuffered chunks become impossible. To avoid this
|
| /Documentation/block/ |
| 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).
|
| 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
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 13 effect of concentrating writes on a single erase block, which can speed
22 speculation is correct (typically the case for full writes of small
25 Under this scheme, when a file needs more blocks to absorb file writes,
|
| /Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 30 or down by additional writes to nfsd/threads or by writes to
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 49 shall implement "true random writes with 2KB granularity", which means
59 host to perform aligned writes at 32KB boundaries. Other drives do
61 writes are not 32KB aligned.
64 generates aligned writes::
|
| /Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
30 This operations are defined as RapidIO Maintenance reads/writes in RIO spec.
42 port-writes or both (RIO_SET_EVENT_MASK/RIO_GET_EVENT_MASK)
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 19 State 1: All writes to the device cause the underlying data to be backed up to
21 However, the writes, with one exception, then happen exactly as they would
25 isn't enough free space, writes are failed with -ENOSPC.
61 writes from the true sector zero are redirected to. Note that like any backup
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic-v3.txt | 77 Writes to read-only registers are ignored by the kernel.
118 Accesses (reads and writes) to the GICD_ISPENDR register region and
127 interrupt is activated or when the guest writes to ICPENDR. A level
130 ISPENDR writes are latched; if the device lowers the line level then the
132 conversely writes to ICPENDR or activations of the interrupt do not clear
147 RAZ/WI semantics, meaning that reads always return 0 and writes are always
|
1234567891011