Searched +full:data +full:- +full:size (Results 1 – 25 of 1058) sorted by relevance
12345678910>>...43
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
9 writing the sector and the integrity tag must be atomic - i.e. in case of
12 To guarantee write atomicity, the dm-integrity target uses journal, it
13 writes sector data and integrity tags into a journal, commits the journal
14 and then copies the data and integrity tags to their respective location.
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
[all …]
|
| D | verity.rst | 2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
7 This target is read-only.
21 This is the type of the on-disk hash format.
32 This is the device containing data, the integrity of which needs to be
37 This is the device that supplies the hash tree data. It may be
40 dm-verity device.
43 The block size on a data device in bytes.
47 The size of a hash block in bytes.
50 The number of data blocks on the data device. Additional blocks are
[all …]
|
| D | zero.rst | 2 dm-zero
5 Device-Mapper's "zero" target provides a block-device that always returns
6 zero'd data on reads and silently drops writes. This is similar behavior to
7 /dev/zero, but as a block-device instead of a character-device.
9 Dm-zero has no target-specific parameters.
11 One very interesting use of dm-zero is for creating "sparse" devices in
12 conjunction with dm-snapshot. A sparse device reports a device-size larger
14 write data anywhere within the sparse device and read it back like a normal
16 enough data has been written to fill up the actual storage space, the sparse
20 To create a sparse device, start by creating a dm-zero device that's the
[all …]
|
| D | vdo.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
3 dm-vdo
6 The dm-vdo (virtual data optimizer) device mapper target provides
7 block-level deduplication, compression, and thin provisioning. As a device
9 with any file system. The vdo target does not protect against data
20 https://github.com/dm-vdo/vdo/
25 enter or come up in read-only mode. Because read-only mode is indicative of
26 data-loss, a positive action must be taken to bring vdo out of read-only
28 prepare a read-only vdo to exit read-only mode. After running this tool,
30 started. Although some data may be lost, the rebuilt vdo's metadata will be
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 9 # mount -t configfs none /sys/kernel/config/
19 configure the buffer size for this channel
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
60 configuration, the creation is post-poned until
74 configure the buffer size for this channel
77 configure the sub-buffer size for this channel
78 (needed for synchronous and isochronous data)
[all …]
|
| D | sysfs-secvar | 22 and is expected to be "ibm,edk2-compat-v1".
26 has the form "ibm,plpks-sb-v<version>", or
27 "ibm,plpks-sb-unknown" if there is no SB_VERSION variable.
34 representation. The data and size can be determined by reading
37 What: /sys/firmware/secvar/vars/<variable_name>/size
40 Description: An integer representation of the size of the content of the
41 variable. In other words, it represents the size of the data.
43 What: /sys/firmware/secvar/vars/<variable_name>/data
46 Description: A read-only file containing the value of the variable. The size
47 of the file represents the maximum size of the variable data.
[all …]
|
| D | sysfs-class-firmware | 1 What: /sys/class/firmware/.../data
5 Description: The data sysfs file is used for firmware-fallback and for
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
27 Description: Read-only. Returns a string describing a failed firmware
31 following: "hw-error", "timeout", "user-abort", "device-busy",
32 "invalid-file-size", "read-write-error", "flash-wearout". The
41 Description: The loading sysfs file is used for both firmware-fallback and
43 you are writing a firmware file to the data sysfs node. Echo
[all …]
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 5 Date : 2004-Nov-26
33 See also "CP Command and Utility Reference" (SC24-6081-00) for more information
35 and Administration" (SC24-6116-00) for more information on DCSSes.
38 -----------
44 This defines two blocks of storage, the first is 140MB in size an begins at
45 address 0MB, the second is 200MB in size and begins at address 200MB,
47 always start at 0 and be at least 64MB in size.
50 -----------
59 This defines 140MB storage size for your guest, the parameter "mem=160M" is
78 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
13 …The following APIs provide access via the Hypervisor to hardware assisted data processing function…
16 live-migration and other system management activities.
18 36.1. Data Analytics Accelerator
19 …The Data Analytics Accelerator (DAX) functionality is a collection of hardware coprocessors that p…
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
21 …the following data query operations: search, extraction, compression, decompression, and translati…
24 …The DAX is a virtual device to sun4v guests, with supported data operations indicated by the virtu…
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 5 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
26 shutdown can cause data in some stripes to not be in consistent state, eg, data
[all …]
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 5 ------------
9 crypto API high level discussion for the in-kernel use cases applies
21 Some details of the in-kernel kernel crypto API aspects do not apply to
29 ------------------------------
34 - Message digest including keyed message digest (HMAC, CMAC)
36 - Symmetric ciphers
38 - AEAD ciphers
40 - Random Number Generators
56 A cipher is accessed with the same name as done for the in-kernel API
80 system calls to send data to the kernel or obtain data from the
[all …]
|
| D | api-samples.rst | 5 -----------------------------------------------
7 This code encrypts some data with AES-256-XTS. For sake of example,
8 all inputs are random bytes, the encryption is done in-place, and it's
17 u8 *data = NULL;
18 const size_t datasize = 512; /* data size in bytes */
21 u8 iv[16]; /* AES-256-XTS takes a 16-byte IV */
22 u8 key[64]; /* AES-256-XTS takes a 64-byte key */
28 * In real-world use, a tfm and key are typically used for many
49 err = -ENOMEM;
53 /* Prepare the input data */
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mvebu-devbus.txt | 9 - compatible: Armada 370/XP SoC are supported using the
10 "marvell,mvebu-devbus" compatible string.
13 "marvell,orion-devbus" compatible string.
15 - reg: A resource specifier for the register space.
20 - #address-cells: Must be set to 1
21 - #size-cells: Must be set to 1
22 - ranges: Must be set up to reflect the memory layout with four
23 integer values for each chip-select line in use:
24 0 <physical address of mapping> <size>
28 - devbus,keep-config This property can optionally be used to keep
[all …]
|
| /Documentation/filesystems/ |
| D | erofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 EROFS - Enhanced Read-Only File System
10 EROFS filesystem stands for Enhanced Read-Only File System. It aims to form a
11 generic read-only filesystem solution for various read-only use cases instead
17 random-access friendly high-performance filesystem to get rid of unneeded I/O
18 amplification and memory-resident overhead compared to similar approaches.
22 - read-only storage media or
24 - part of a fully trusted read-only solution, which means it needs to be
25 immutable and bit-for-bit identical to the official golden image for
28 - hope to minimize extra storage space with guaranteed end-to-end performance
[all …]
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | microchip,93lc46b.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Cory Tusar <cory.tusar@pid1solutions.com>
15 - atmel,at93c46
16 - atmel,at93c46d
17 - atmel,at93c56
18 - atmel,at93c66
19 - eeprom-93xx46
20 - microchip,93lc46b
[all …]
|
| /Documentation/core-api/ |
| D | librs.rst | 2 Reed-Solomon Library Programming Interface
10 The generic Reed-Solomon Library provides encoding, decoding and error
13 Reed-Solomon codes are used in communication and storage applications to
14 ensure data integrity.
30 ------------
54 --------
56 The encoder calculates the Reed-Solomon code over the given data length
60 The expanded data can be inverted on the fly by providing a non-zero
61 inversion mask. The expanded data is XOR'ed with the mask. This is used
63 Reed-Solomon code for all 0x00 is all 0x00. The code is inverted before
[all …]
|
| D | swiotlb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 the CPU copies the data between the temporary buffer and the original target
19 These APIs use the device DMA attributes and kernel-wide settings to determine
24 Because the CPU copies data between the bounce buffer and the original target
30 ---------------
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
44 data to/from the original target memory buffer. The CPU copying bridges between
52 the data being transferred. But if that memory occupies only part of an IOMMU
53 granule, other parts of the granule may contain unrelated kernel data. Since
[all …]
|
| /Documentation/filesystems/caching/ |
| D | netfs-api.rst | 1 .. 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/sound/designs/ |
| D | compress-accel.rst | 2 ALSA Co-processor Acceleration API
16 is able to handle "tasks" that are not bound to real-time operations
24 - serialization of multiple tasks for user space to allow multiple
27 - separate buffers (input + output) for each operation
29 - expose buffers using mmap to user space
31 - signal user space when the task is finished (standard poll mechanism)
47 Data I/O mechanism is using standard dma-buf interface with all advantages
49 input data and second (separate) buffer is used for the output data. Each task
53 for given device. The fragment_size limits the input buffer size for the given
54 device. The output buffer size is determined by the driver (may be different
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,qe-muram.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/fsl/cpm_qe/fsl,qe-muram.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale QUICC Engine Multi-User RAM (MURAM)
10 - Frank Li <Frank.Li@nxp.com>
12 description: Multi-User RAM (MURAM)
17 - const: fsl,qe-muram
18 - const: fsl,cpm-muram
23 "#address-cells":
[all …]
|
| /Documentation/admin-guide/ |
| D | bcache.rst | 11 This is the git repository of bcache-tools:
12 https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-tools.git/
17 It's designed around the performance characteristics of SSDs - it only allocates
19 extents (which can be anywhere from a single sector to the bucket size). It's
25 great lengths to protect your data - it reliably handles unclean shutdown. (It
29 Writeback caching can use most of the cache for buffering writes - writing
30 dirty data to the backing device is always done sequentially, scanning from the
36 average is above the cutoff it will skip all IO from that task - instead of
40 In the event of a data IO error on the flash it will try to recover by reading
41 from disk or invalidating cache entries. For unrecoverable errors (meta data
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom,coresight-tpdm.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/qcom,coresight-tpdm.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Trace, Profiling and Diagnostics Monitor - TPDM
11 The TPDM or Monitor serves as data collection component for various dataset
13 Basic Counts (BC), Tenure Counts (TC), Continuous Multi-Bit (CMB), and Discrete
14 Single Bit (DSB). It performs data collection in the data producing clock
15 domain and transfers it to the data collection time domain, generally ATB
18 The primary use case of the TPDM is to collect data from different data
[all …]
|
| /Documentation/devicetree/bindings/net/can/ |
| D | cc770.txt | 8 - compatible : should be "bosch,cc770" for the CC770 and "intc,82527"
11 - reg : should specify the chip select, address offset and size required
12 to map the registers of the controller. The size is usually 0x80.
14 - interrupts : property with a value describing the interrupt source
19 - bosch,external-clock-frequency : frequency of the external oscillator
24 - bosch,clock-out-frequency : slock frequency in Hz on the CLKOUT pin.
28 - bosch,slew-rate : slew rate of the CLKOUT signal. If not specified,
31 - bosch,disconnect-rx0-input : see data sheet.
33 - bosch,disconnect-rx1-input : see data sheet.
35 - bosch,disconnect-tx1-output : see data sheet.
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | nvidia,tegra20-gmi.txt | 10 - compatible : Should contain one of the following:
11 For Tegra20 must contain "nvidia,tegra20-gmi".
12 For Tegra30 must contain "nvidia,tegra30-gmi".
13 - reg: Should contain GMI controller registers location and length.
14 - clocks: Must contain an entry for each entry in clock-names.
15 - clock-names: Must include the following entries: "gmi"
16 - resets : Must contain an entry for each entry in reset-names.
17 - reset-names : Must include the following entries: "gmi"
18 - #address-cells: The number of cells used to represent physical base
20 - #size-cells: The number of cells used to represent the size of an address
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | gpio-control-nand.txt | 4 read/write the NAND commands and data and GPIO pins for the control
8 - compatible : "gpio-control-nand"
9 - reg : should specify localbus chip select and size used for the chip. The
10 resource describes the data bus connected to the NAND flash and all accesses
12 - #address-cells, #size-cells : Must be present if the device has sub-nodes
14 - gpios : Specifies the GPIO pins to control the NAND device. The order of
18 - bank-width : Width (in bytes) of the device. If not present, the width
20 - chip-delay : chip dependent delay for transferring data from array to
22 - gpio-control-nand,io-sync-reg : A 64-bit physical address for a read
24 the GPIO's and the NAND flash data bus. If present, then after changing
[all …]
|
12345678910>>...43