Home
last modified time | relevance | path

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

12345678910>>...31

/Documentation/driver-api/md/
Draid5-cache.rst5 Raid 4/5/6 could include an extra disk for data cache besides normal RAID
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
[all …]
Draid5-ppl.rst7 may become inconsistent with data on other member disks. If the array is also
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
19 which chunk writes have completed. If one of the not modified data disks of
[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)
18 data using the `bmfdec <https://github.com/pali/bmfdec>`_ utility:
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];
38 guid("{ABBC0F6E-8EA1-11d1-00A0-C90629100000}")]
43 [WmiMethodId(1), Implemented, read, write, Description("Return the contents of a package")]
44 void GetPackage([out, id(0)] Package Data);
[all …]
Ddell-wmi-ddv.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
4 Dell DDV WMI interface driver (dell-wmi-ddv)
10 Many Dell notebooks made after ~2020 support a WMI-based interface for
11 retrieving various system data like battery temperature, ePPID, diagnostic data
12 and fan/thermal sensor data.
14 This interface is likely used by the `Dell Data Vault` software on Windows,
15 so it was called `DDV`. Currently the ``dell-wmi-ddv`` driver supports
21 trial-and-error, please keep that in mind.
27 including batteries. It has a form similar to `CC-PPPPPP-MMMMM-YMD-SSSS-FFF`
48 data using the `bmfdec <https://github.com/pali/bmfdec>`_ utility:
[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,gpmc-child.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ti,gpmc-child.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tony Lindgren <tony@atomide.com>
11 - Roger Quadros <rogerq@kernel.org>
24 gpmc,sync-clk-ps:
28 # Chip-select signal timings corresponding to GPMC_CONFIG2:
29 gpmc,cs-on-ns:
33 gpmc,cs-rd-off-ns:
[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
45 When the application does not provide more data in time, the previous
[all …]
Dio.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 The V4L2 API defines several different methods to read from or write to
10 a device. All drivers exchanging data with applications must support at
14 :c:func:`write()` function is automatically selected after opening a
16 read or write will fail at any time.
23 application does not directly receive the image data. It is selected by
29 exchanging data with a driver ("panel applications", see :ref:`open`)
36 method (after first switching away from read/write) other than by
49 field-order
Drw.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
7 Read/Write
11 :c:func:`write()` function, respectively, when the
16 Drivers may need the CPU to copy the data, but they may also support DMA
19 considered inferior though because no meta-information like frame
21 recognize frame dropping and to synchronize with other data streams.
23 setup to exchange data. It permits command line stunts like this (the
26 .. code-block:: none
28 $ vidctrl /dev/video --input=0 --format=YUYV --size=352x288
32 function, to write the :c:func:`write()` function. Drivers
[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
43 The exact format of the data depends on what mode a driver is in, use
47 When in :ref:`LIRC_MODE_PULSE <lirc-mode-PULSE>` mode, the data written to
[all …]
/Documentation/ABI/testing/
Dconfigfs-most9 # mount -t configfs none /sys/kernel/config/
22 configure the sub-buffer size for this channel
23 (needed for synchronous and isochronous data)
31 configure type of data that will travel over
39 configure DBR data buffer size (this is used
58 write '1' to this attribute to trigger the
60 configuration, the creation is post-poned until
64 write '1' to this attribute to destroy an
77 configure the sub-buffer size for this channel
78 (needed for synchronous and isochronous data)
[all …]
Dsysfs-class-firmware1 What: /sys/class/firmware/.../data
5 Description: The data sysfs file is used for firmware-fallback and for
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
31 following: "hw-error", "timeout", "user-abort", "device-busy",
[all …]
/Documentation/filesystems/spufs/
Dspufs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
21 message queues. Users that have write permissions on the file system
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).
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
65 data in the address space of the SPU. The possible operations on an
68 read(2), pread(2), write(2), pwrite(2), lseek(2)
[all …]
/Documentation/admin-guide/device-mapper/
Dvdo-design.rst1 .. SPDX-License-Identifier: GPL-2.0-only
4 Design of dm-vdo
7 The dm-vdo (virtual data optimizer) target provides inline deduplication,
8 compression, zero-block elimination, and thin provisioning. A dm-vdo target
12 production environments ever since. It was made open-source in 2017 after
14 dm-vdo. For usage, see vdo.rst in the same directory as this file.
25 The design of dm-vdo is based on the idea that deduplication is a two-part
26 problem. The first is to recognize duplicate data. The second is to avoid
27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main
29 duplicate data, and a data store with a reference counted block map that
[all …]
Ddm-zoned.rst2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
6 ZAC compliant devices) as a regular block device without any write
7 pattern constraints. In effect, it implements a drive-managed zoned
9 doing raw block device accesses) the sequential write constraints of
10 host-managed zoned block devices and can mitigate the potential
11 device-side performance degradation due to excessive random writes on
12 host-aware zoned block devices.
21 http://www.t13.org/Documents/UploadedDocuments/docs2015/di537r05-Zoned_Device_ATA_Command_Set_ZAC.p…
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
[all …]
Dwritecache.rst14 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
41 autocommit time in milliseconds. The data is automatically
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
[all …]
/Documentation/hwmon/
Dabituguru-datasheet.rst6 datasheet from Abit. The data I have got on uGuru have I assembled through
11 mailing Windbond for help won't give any useful data about uGuru, as it is
14 Olle Sandberg <ollebull@gmail.com>, 2005-05-25
19 and extended with write support and info on more databanks, the write support
27 Hans de Goede <j.w.r.degoede@hhs.nl>, 28-01-2006
33 As far as known the uGuru is always placed at and using the (ISA) I/O-ports
34 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two
35 ports are holding for detection. We will refer to 0xE0 as CMD (command-port)
36 and 0xE4 as DATA because Abit refers to them with these names.
38 If DATA holds 0x00 or 0x08 and CMD holds 0x00 or 0xAC an uGuru could be
[all …]
/Documentation/i2c/
Dsmbus-protocol.rst14 If you write a driver for some I2C device, please try to use the SMBus
24 single data byte, the functions using SMBus protocol operation names execute
39 Sr Repeated start condition, used to switch from write to
42 Rd/Wr (1 bit) Read/Write bit. Rd equals 1, Wr equals 0.
46 Comm (8 bits) Command byte, a data byte which often selects a register on
48 Data (8 bits) A plain data byte. DataLow and DataHigh represent the low and
50 Count (8 bits) A data byte containing the length of a block operation.
52 [..] Data sent by I2C device, as opposed to data sent by the host
77 S Addr Rd [A] [Data] NA P
92 S Addr Wr [A] Data [A] P
[all …]
/Documentation/networking/
Doa-tc6-framework.rst1 .. SPDX-License-Identifier: GPL-2.0+
4 OPEN Alliance 10BASE-T1x MAC-PHY Serial Interface (TC6) Framework Support
8 ------------
11 single pair of conductors. The 10BASE-T1L (Clause 146) is a long reach
12 PHY supporting full duplex point-to-point operation over 1 km of single
13 balanced pair of conductors. The 10BASE-T1S (Clause 147) is a short reach
14 PHY supporting full / half duplex point-to-point operation over 15 m of
21 works in conjunction with the 10BASE-T1S PHY operating in multidrop mode.
23 The aforementioned PHYs are intended to cover the low-speed / low-cost
29 The MAC-PHY solution integrates an IEEE Clause 4 MAC and a 10BASE-T1x PHY
[all …]
/Documentation/devicetree/bindings/serio/
Dps2-gpio.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serio/ps2-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Danilo Krummrich <danilokrummrich@dk-develop.de>
14 const: ps2-gpio
16 data-gpios:
18 the gpio used for the data signal - this should be flagged as
20 from <dt-bindings/gpio/gpio.h> since the signal is open drain by
24 clk-gpios:
[all …]
/Documentation/i2c/busses/
Di2c-mlxcpld.rst2 Driver i2c-mlxcpld
11 - Master mode.
12 - One physical bus.
13 - Polling mode.
20 - Receive Byte/Block.
21 - Send Byte/Block.
22 - Read Byte/Block.
23 - Write Byte/Block.
28 CPBLTY 0x0 - capability reg.
29 Bits [6:5] - transaction length. b01 - 72B is supported,
[all …]
/Documentation/filesystems/caching/
Dnetfs-api.rst1 .. SPDX-License-Identifier: GPL-2.0
10 (1) A cache is logically organised into volumes and data storage objects
13 (2) Volumes and data storage objects are represented by various types of
18 (4) Cookies have coherency data that allows a cache to determine if the
19 cached data is still valid.
31 (3) Data file registration
33 (5) Resizing a data file (truncation)
34 (6) Data I/O API
35 (7) Data file coherency
36 (8) Data file invalidation
[all …]
/Documentation/kernel-hacking/
Dfalse-sharing.rst1 .. SPDX-License-Identifier: GPL-2.0
9 False sharing is related with cache mechanism of maintaining the data
22 +-----------+ +-----------+
24 +-----------+ +-----------+
28 +----------------------+ +----------------------+
30 +----------------------+ +----------------------+
32 ---------------------------+------------------+-----------------------------
34 +----------------------+
36 +----------------------+
38 +----------------------+
[all …]
/Documentation/w1/masters/
Dds2490.rst13 -----------
16 which allows to build USB <-> W1 bridges.
18 DS9490(R) is a USB <-> W1 bus master device
20 low-level operational chip.
24 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
27 - The hardware will detect when devices are attached to the bus on the
31 - The number of USB bus transactions could be reduced if w1_reset_send
33 a write buffer and a read buffer (along with sizes) as arguments.
34 The ds2490 block I/O command supports reset, write buffer, read
[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
14 A data set is consistent when the sequence count at the beginning of the
16 read again at the end of the critical section. The data in the set must
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
30 interrupted writer. If that reader belongs to a real-time scheduling
33 This mechanism cannot be used if the protected data contains pointers,
43 multiple writers. Write side critical sections must thus be serialized
[all …]

12345678910>>...31