Home
last modified time | relevance | path

Searched +full:write +full:- +full:to +full:- +full:write (Results 1 – 25 of 1023) sorted by relevance

12345678910>>...41

/Documentation/driver-api/md/
Draid5-cache.rst7 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
10 refer to mdadm manual for details. By default (RAID array starts), the cache is
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
19 In both modes, all writes to the array will hit cache disk first. This means
22 write-through mode
[all …]
Draid5-ppl.rst8 in degraded state, there is no way to recalculate parity, because one of the
9 disks is missing. This can lead to silent data corruption when rebuilding the
10 array or using it is as degraded - data calculated from parity for array blocks
11 that have not been touched by a write request during the unclean shutdown can
12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
15 Partial parity for a write operation is the XOR of stripe data chunks not
16 modified by this write. It is just enough data needed for recovering from the
17 write hole. XORing partial parity with the modified chunks produces parity for
18 the stripe, consistent with its state before the write operation, regardless of
20 this stripe is missing, this updated parity can be used to recover its
[all …]
/Documentation/ABI/testing/
Dsysfs-class-bdi14 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
39 writeout speed in relation to the other devices.
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
[all …]
Dsysfs-driver-xdata1 What: /sys/class/misc/drivers/dw-xdata-pcie.<device>/write
5 Description: Allows the user to enable the PCIe traffic generator which
6 will create write TLPs frames - from the Root Complex to the
7 Endpoint direction or to disable the PCIe traffic generator
10 Write y/1/on to enable, n/0/off to disable
13 echo 1 > /sys/class/misc/dw-xdata-pcie.<device>/write
15 echo 0 > /sys/class/misc/dw-xdata-pcie.<device>/write
21 cat /sys/class/misc/dw-xdata-pcie.<device>/write
24 The file is read and write.
26 What: /sys/class/misc/dw-xdata-pcie.<device>/read
[all …]
Dconfigfs-spear-pcie-gadget1 What: /config/pcie-gadget
7 Interface is used to configure selected dual mode PCIe controller
8 as device and then program its various registers to configure it
10 This interfaces can be used to show spear's PCIe device capability.
12 Nodes are only visible when configfs is mounted. To mount configfs
15 # mount -t configfs none /config/
17 For nth PCIe Device Controller /config/pcie-gadget.n/:
20 link used to enable ltssm and read its status.
21 int_type used to configure and read type of supported interrupt
22 no_of_msi used to configure number of MSI vector needed and
[all …]
Dsysfs-block-zram5 The disksize file is read-write and specifies the disk size
14 The initstate file is read-only and shows the initialization
21 The reset file is write-only and allows resetting the
29 The max_comp_streams file is read-write and specifies the
37 The comp_algorithm file is read-write and lets to show
45 The mem_used_max file is write-only and is used to reset
46 the counter of maximum memory zram have consumed to store
47 compressed data. For resetting the value, you should write
48 "0". Otherwise, you could see -EINVAL.
55 The mem_limit file is write-only and specifies the maximum
[all …]
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
48 Description: (Read) Output trigger signals to connected device <N>
[all …]
Dsysfs-platform-dfl-port1 What: /sys/bus/platform/devices/dfl-port.0/id
5 Description: Read-only. It returns id of this port. One DFL FPGA device
6 may have more than one port. Userspace could use this id to
9 What: /sys/bus/platform/devices/dfl-port.0/afu_id
13 Description: Read-only. User can program different PR bitstreams to FPGA
15 returns uuid which could be used to identify which PR bitstream
18 What: /sys/bus/platform/devices/dfl-port.0/power_state
22 Description: Read-only. It reports the APx (AFU Power) state, different APx
24 returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.
26 What: /sys/bus/platform/devices/dfl-port.0/ap1_event
[all …]
Dsysfs-class-firmware5 Description: The data sysfs file is used for firmware-fallback and for
6 firmware uploads. Cat a firmware image to this sysfs file
7 after you echo 1 to the loading sysfs file. When the firmware
8 image write is complete, echo 0 to the loading sysfs file. This
9 sequence will signal the completion of the firmware write and
10 signal the lower-level driver that the firmware data is
17 Description: Write-only. For firmware uploads, write a "1" to this file to
18 request that the transfer of firmware data to the lower-level
20 the update cannot be canceled (e.g. a FLASH write is in
27 Description: Read-only. Returns a string describing a failed firmware
[all …]
/Documentation/userspace-api/media/v4l/
Dfunc-write.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-write:
7 V4L2 write()
13 v4l2-write - Write to a V4L2 device
18 .. code-block:: c
22 .. c:function:: ssize_t write( int fd, void *buf, size_t count )
31 Buffer with data to be written
39 :c:func:`write()` writes up to ``count`` bytes to the device
42 enables them. When ``count`` is zero, :c:func:`write()` returns 0
54 nothing was written. On error, -1 is returned, and the ``errno``
[all …]
/Documentation/wmi/devices/
Dmsi-wmi-platform.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
4 MSI WMI Platform Features driver (msi-wmi-platform)
24 guid("{ABBC0F60-8EA1-11d1-00A0-C90629100000}")]
26 [WmiDataId(1), read, write, Description("16 bytes of data")] uint8 Bytes[16];
31 guid("{ABBC0F63-8EA1-11d1-00A0-C90629100000}")]
33 [WmiDataId(1), read, write, Description("32 bytes of data")] uint8 Bytes[32];
37 Description("Class used to operate methods on a package"),
38 guid("{ABBC0F6E-8EA1-11d1-00A0-C90629100000}")]
43 [WmiMethodId(1), Implemented, read, write, Description("Return the contents of a package")]
46 [WmiMethodId(2), Implemented, read, write, Description("Set the contents of a package")]
[all …]
/Documentation/filesystems/
Dzonefs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
12 device support (e.g. f2fs), zonefs does not hide the sequential write
13 constraint of zoned block devices to the user. Files representing sequential
14 write zones of the device must be written sequentially starting from the end
17 As such, zonefs is in essence closer to a raw block device access interface
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
21 direct block device file ioctls which may be more obscure to developers. One
22 example of this approach is the implementation of LSM (log-structured merge)
[all …]
Dfuse-io.rst1 .. 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
23 after any writes to the file. All mmap modes are supported.
[all …]
/Documentation/ABI/stable/
Dsysfs-bus-nvmem6 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/scsi/
Dsd-parameters.rst1 .. 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
24 To modify the caching mode without making the change persistent, prepend
[all …]
/Documentation/bpf/
Dprog_cgroup_sysctl.rst1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 provides cgroup-bpf hook for sysctl.
10 The hook has to be attached to a cgroup and will be called every time a
11 process inside that cgroup tries to read from or write to sysctl knob in proc.
16 ``BPF_CGROUP_SYSCTL`` attach type has to be used to attach
17 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program to a cgroup.
22 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` provides access to the following context from
26 __u32 write;
30 * ``write`` indicates whether sysctl value is being read (``0``) or written
31 (``1``). This field is read-only.
[all …]
/Documentation/locking/
Dseqlock.rst8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
10 are used for data that's rarely written to (e.g. system time), where the
11 reader wants a consistent set of information and is willing to retry if
23 is odd and indicates to the readers that an update is in progress. At
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
29 the entire scheduler tick due to the odd sequence count value and the
30 interrupted writer. If that reader belongs to a real-time scheduling
43 multiple writers. Write side critical sections must thus be serialized
[all …]
/Documentation/userspace-api/media/rc/
Dlirc-write.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _lirc-write:
7 LIRC write()
13 lirc-write - Write to a LIRC device
18 .. code-block:: c
22 .. c:function:: ssize_t write( int fd, void *buf, size_t count )
31 Buffer with data to be written
39 :c:func:`write()` writes up to ``count`` bytes to the device
44 :ref:`lirc_get_features` to get the supported modes and use
47 When in :ref:`LIRC_MODE_PULSE <lirc-mode-PULSE>` mode, the data written to
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dst,stm32-fmc2-ebi-props.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/st,stm32-fmc2-ebi-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christophe Kerello <christophe.kerello@foss.st.com>
11 - Marek Vasut <marex@denx.de>
14 st,fmc2-ebi-cs-transaction-type:
25 8: Synchronous read synchronous write PSRAM.
26 9: Synchronous read asynchronous write PSRAM.
27 10: Synchronous read synchronous write NOR.
[all …]
Dti-aemif.txt3 The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
[all …]
/Documentation/admin-guide/device-mapper/
Dlog-writes.rst2 dm-log-writes
5 This target takes 2 devices, one to pass all IO to normally, and one to log all
6 of the write operations to. This is intended for file system developers wishing
7 to verify the integrity of metadata or data as the file system is written to.
8 There is a log_write_entry written for every WRITE request and the target is
9 able to take arbitrary data from userspace to insert into the log. The data
10 that is in the WRITE requests is copied into the log to make the replay happen
16 We log things in order of completion once we are sure the write is no longer in
17 cache. This means that normal WRITE requests are not actually logged until the
18 next REQ_PREFLUSH request. This is to make it easier for userspace to replay
[all …]
/Documentation/filesystems/spufs/
Dspufs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
17 Broadband Engine Architecture in order to access Synergistic Processor
20 The file system provides a name space similar to posix shared memory or
21 message queues. Users that have write permissions on the file system
22 can use spu_create(2) to establish SPU contexts in the spufs root.
26 logical SPU. Users can change permissions on those files, but not actu-
43 The files in spufs mostly follow the standard behavior for regular sys-
44 tem calls like read(2) or write(2), but often support only a subset of
50 all files that support the write(2) operation also support writev(2).
[all …]
/Documentation/devicetree/bindings/w1/
Dw1-uart.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/w1/w1-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: UART 1-Wire Bus
10 - Christoph Winklhofer <cj.winklhofer@gmail.com>
13 UART 1-wire bus. Utilizes the UART interface via the Serial Device Bus
14 to create the 1-Wire timing patterns.
16 The UART peripheral must support full-duplex and operate in open-drain
18 baud-rate and transmitted byte, which corresponds to a 1-Wire read bit,
[all …]
/Documentation/hwmon/
Doxp-sensors.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver oxp-sensors
7 - Derek John Clark <derekjohn.clark@gmail.com>
8 - Joaquín Ignacio Aramendía <samsagax@gmail.com>
11 ------------
27 -----------------
31 - AOKZOE A1
32 - AOKZOE A1 PRO
33 - AYANEO 2
34 - AYANEO 2S
[all …]
/Documentation/arch/x86/
Dmtrr.rst1 .. 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
16 arch_phys_wc_add() in combination with ioremap_wc() to make MTRR effective on
17 non-PAT systems while a no-op but equally effective on PAT enabled systems.
21 firmware may still have implemented access to MTRRs which would be controlled
24 the platform code would need uncachable access to some of its fan control
26 place other than mtrr_type_lookup() to ensure any OS specific mapping requests
31 For details refer to Documentation/arch/x86/pat.rst.
35 the Memory Type Range Registers (MTRRs) may be used to control
[all …]

12345678910>>...41