Searched +full:write +full:- +full:back (Results 1 – 25 of 330) sorted by relevance
12345678910>>...14
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 7 caches data to the RAID disks. The cache can be in write-through (supported
8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
9 3.4) has a new option '--write-journal' to create array with cache. Please
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
17 echo "write-through" > /sys/block/md0/md/journal_mode
22 write-through mode
25 This mode mainly fixes the 'write hole' issue. For RAID 4/5/6 array, an unclean
27 and parity don't match. The reason is that a stripe write involves several RAID
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS
17 MAJOR:MINOR-fuseblk
23 The default backing dev, used for non-block device backed
30 Size of the read-ahead window in kilobytes
32 (read-write)
38 total write-back cache that relates to its current average
42 percentage of the write-back cache to a particular device.
45 (read-write)
52 total write-back cache that relates to its current average
56 of the write-back cache to a particular device. The value is
[all …]
|
| D | debugfs-scmi-raw | 5 Description: SCMI Raw synchronous message injection/snooping facility; write
7 in little-endian binary format to have it sent to the configured
11 Each write to the entry causes one command request to be built
12 and sent while the replies are read back one message at time
20 Description: SCMI Raw asynchronous message injection/snooping facility; write
22 in little-endian binary format to have it sent to the configured
29 Each write to the entry causes one command request to be built
30 and sent while the replies are read back one message at time
38 Description: SCMI Raw message errors facility; any kind of timed-out or
41 Each read gives back one message at time (receiving an EOF at
[all …]
|
| D | sysfs-platform-hidma-mgmt | 1 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
10 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/weight
19 What: /sys/devices/platform/hidma-mgmt*/chreset_timeout_cycles
31 What: /sys/devices/platform/hidma-mgmt*/dma_channels
40 What: /sys/devices/platform/hidma-mgmt*/hw_version_major
48 What: /sys/devices/platform/hidma-mgmt*/hw_version_minor
56 What: /sys/devices/platform/hidma-mgmt*/max_rd_xactions
63 read transactions that can be issued back to back.
68 What: /sys/devices/platform/hidma-mgmt*/max_read_request
77 What: /sys/devices/platform/hidma-mgmt*/max_wr_xactions
[all …]
|
| D | sysfs-ptp | 41 Write integer to re-configure it.
80 value back to 0 deletes the virtual clocks and
81 switches the physical clock back to normal, adjustable
110 This write-only file enables or disables external
111 timestamps. To enable external timestamps, write the
113 To disable external timestamps, write the channel
128 This write-only file enables or disables periodic
129 outputs. To enable a periodic output, write five
139 This write-only file enables or disables delivery of
141 events, write a "1" into the file. To disable events,
[all …]
|
| D | sysfs-bus-most | 8 might return <1-1.1:1.0>
26 write the controller's DCI registers.
35 application wants to read from or write to.
43 This is used to read and write the DCI register whose address
220 This is to read back the configured number of buffers of
229 This is to read back the configured buffer size of the channel.
237 This is to read back the configured direction of the channel.
249 This is to read back the configured data type of the channel.
263 This is to read back the configured subbuffer size of
272 This is to read back the configured number of packets per
|
| D | sysfs-platform-dell-laptop | 9 light sensor. Write 1 to this file to enable the auto
31 enabled are preceded by '+', those disabled by '-'.
33 To enable a trigger, write its name preceded by '+' to
34 this file. To disable a trigger, write its name preceded
35 by '-' instead.
43 echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
59 To configure the timeout, write to this file a value along
72 some systems might fall back to a specific timeout in case
|
| D | sysfs-driver-intel_sdsi | 38 is available at http://github.com/intel/intel-sdsi
49 http://github.com/intel/intel-sdsi
56 (WO) Used to write an Authentication Key Certificate (AKC) to
65 (WO) Used to write a Capability Activation Payload (CAP) to the
77 (RO) Used to read back the current meter certificate for the CPU
87 (RO) Used to read back the current state certificate for the CPU
|
| /Documentation/scsi/ |
| D | sd-parameters.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ---------------
9 Enable/disable drive write & read cache.
12 cache_type string WCE RCD Write cache Read cache
14 write through 0 0 off on
16 write back 1 0 on on
17 write back, no read (daft) 1 1 on off
20 To set cache type to "write back" and save this setting to the drive::
22 # echo "write back" > cache_type
27 # echo "temporary write back" > cache_type
|
| /Documentation/arch/x86/ |
| D | mtrr.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Richard Gooch <rgooch@atnf.csiro.au> - 3 Jun 1999
8 - Luis R. Rodriguez <mcgrof@do-not-panic.com> - April 9, 2015
17 non-PAT systems while a no-op but equally effective on PAT enabled systems.
37 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
38 allows bus write transfers to be combined into a larger transfer
40 of image write operations 2.5 times or more.
46 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
50 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
62 which allows you to read and write. The other is an ioctl()
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | writecache.rst | 14 1. type of the cache device - "p" or "s"
15 - p - persistent memory
16 - s - SSD
25 offset from the start of cache device in 512-byte sectors
45 applicable only to persistent memory - use the FUA flag
46 when writing data from persistent memory back to the
49 applicable only to persistent memory - don't use the FUA
50 flag when writing back data and send the FLUSH request
53 - some underlying devices perform better with fua, some
64 dm-writecache target and replace it with dm-linear or
[all …]
|
| D | cache.rst | 8 dm-cache is a device mapper target written by Joe Thornber, Heinz
15 This device-mapper solution allows us to insert this caching at
17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
23 The decision as to what data to migrate and when is left to a plug-in
46 Sub-devices
47 -----------
52 1. An origin device - the big, slow one.
54 2. A cache device - the small, fast one.
56 3. A small metadata device - records which blocks are in the cache,
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-nvmem | 6 This read/write attribute allows users to set read-write
7 devices as read-only and back to read-write from userspace.
8 This can be used to unlock and relock write-protection of
11 Read returns '0' or '1' for read-write or read-only modes
13 Write parses one of 'YyTt1NnFf0', or [oO][NnFf] for "on"
23 This file allows user to read/write the raw NVMEM contents.
24 Permissions for write to this file depends on the nvmem
46 This read-only attribute allows user to read the NVMEM
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 16 -----------
49 -1 if at least one sensor still in conversion, 1 if conversion is complete
60 adjust it (write). A temperature conversion time depends on the device type and
67 completion. Options 2, 3 can't be used in parasite power mode. To get back to
68 the default conversion time write ``0`` to ``conv_time``.
72 the sensor. Resolution is reset when the sensor gets power-cycled.
74 To store the current resolution in EEPROM, write ``0`` to ``w1_slave``.
81 Some non-genuine DS18B20 chips are fixed in 12-bit mode only, so the actual
82 resolution is read back from the chip and verified.
86 The write-only sysfs entry ``eeprom_cmd`` is an alternative for EEPROM operations.
[all …]
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 2 Explicit volatile write back cache control
6 ------------
9 write back caches. That means the devices signal I/O completion to the
10 operating system before data actually has hit the non-volatile storage. This
12 system needs to force data out to the non-volatile storage when it performs
21 ----------------------
26 guarantees that previously completed write requests are on non-volatile
34 ------------------
38 signaled after the data has been committed to non-volatile storage.
42 --------------------------------------
[all …]
|
| /Documentation/filesystems/ |
| D | fuse-io.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - direct-io
10 - cached
11 + write-through
12 + writeback-cache
14 The direct-io mode can be selected with the FOPEN_DIRECT_IO flag in the
17 In direct-io mode the page cache is completely bypassed for reads and writes.
18 No read-ahead takes place. Shared mmap is disabled by default. To allow shared
22 read-ahead by the kernel to fill the cache. The cache is always kept consistent
26 write-through mode is the default and is supported on all kernels. The
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-pyra | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
26 range 0-4.
31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
43 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
57 When written, this file lets one write the respective profile
58 buttons back to the mouse. The data has to be 19 bytes long.
60 Which profile to write is determined by the profile number
66 …usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num…
[all …]
|
| D | sysfs-driver-hid-roccat-konepure | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
13 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
29 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
46 When written, this file lets one write the respective profile
47 buttons back to the mouse. The data has to be 59 bytes long.
49 Which profile to write is determined by the profile number
55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
62 When written, this file lets one write the respective profile
[all …]
|
| D | sysfs-driver-hid-roccat-kovaplus | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
4 Description: The integer value of this attribute ranges from 1-4.
11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
14 Description: The integer value of this attribute ranges from 0-4.
22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
25 Description: The integer value of this attribute ranges from 1-10.
32 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
35 Description: The integer value of this attribute ranges from 1-10.
42 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
54 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | zswap.rst | 10 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles
11 for potentially reduced swap I/O. This trade-off can also result in a
24 drastically reducing life-shortening writes.
41 being swapped out. However, it will _not_ immediately write out or fault
42 back into memory all of the pages stored in the compressed pool. The
44 either invalidated or faulted back into memory. In order to force all
46 fault back into memory all swapped out pages, including those in the
53 evict pages from its own compressed pool on an LRU basis and write them back to
69 means the compression ratio will always be 2:1 or worse (because of half-full
76 with a red-black tree per swap type. The swap offset is the search key for the
[all …]
|
| /Documentation/admin-guide/media/ |
| D | raspberrypi-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be)
7 The PiSP Back End
10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads
13 pixel data back to memory through two distinct output channels.
18 The PiSP Back End ISP processes images in tiles. The handling of image
19 tessellation and the computation of low-level configuration parameters is
24 an image sensor through a MIPI CSI-2 compatible capture interface, storing them
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
29 The pisp-be driver
[all …]
|
| /Documentation/trace/ |
| D | ring-buffer-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.2-no-invariants-only
19 ---------------------------------
22 - where new writes happen in the ring buffer.
25 - where new reads happen in the ring buffer.
28 - the task that writes into the ring buffer (same as writer)
31 - same as producer
34 - the task that reads from the buffer (same as reader)
37 - same as consumer.
40 - A page outside the ring buffer used solely (for the most part)
44 - a pointer to the page that the reader will use next
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-function.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 However with the addition of EP-core in linux kernel, it is possible
34 and read back from MAGIC register to verify BAR0.
46 Bit 2 raise MSI-X IRQ
48 Bit 4 write command (write data to RC buffer)
61 Bit 2 write success
62 Bit 3 write fail
78 the COPY/WRITE command.
83 for the READ/WRITE/COPY and raise IRQ (Legacy/MSI) commands.
90 MSI-X 2
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | intel,ldma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - chuanhua.lei@intel.com
11 - mallikarjunax.reddy@intel.com
14 - $ref: dma-controller.yaml#
19 - intel,lgm-cdma
20 - intel,lgm-dma2tx
21 - intel,lgm-dma1rx
22 - intel,lgm-dma1tx
[all …]
|
| /Documentation/w1/ |
| D | w1-netlink.rst | 21 [struct cn_msg] - connector header.
23 [struct w1_netlink_msg] - w1 netlink header.
24 __u8 type - message type.
36 (read/write/touch)
37 __u8 status - error indication from kernel
38 __u16 len - size of data attached to this header data
40 __u8 id[8]; - slave unique device id
42 __u32 id; - master's id
43 __u32 res; - reserved
47 [struct w1_netlink_cmd] - command for given master or slave device.
[all …]
|
12345678910>>...14