Searched full:data (Results 1 – 25 of 1694) sorted by relevance
12345678910>>...68
| /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
26 shutdown can cause data in some stripes to not be in consistent state, eg, data
29 unclean shutdown. We call an array degraded if it has inconsistent data. MD
31 resync completes, any system crash will expose the chance of real data
34 The write-through cache will cache all data on cache disk first. After the data
35 is safe on the cache disk, the data will be flushed onto RAID disks. The
36 two-step write will guarantee MD can recover correct data after unclean
40 filesystems) after the data is safe on RAID disks, so cache disk failure
41 doesn't cause data loss. Of course cache disk failure means the array is
[all …]
|
| D | raid5-ppl.rst | 7 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
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
19 which chunk writes have completed. If one of the not modified data disks of
26 When handling a write request PPL writes partial parity before new data and
35 not a true journal. It does not protect from losing in-flight data, only from
36 silent data corruption. If a dirty disk of a stripe is lost, no PPL recovery is
38 arbitrary data in the written part of a stripe if that disk is lost. In such
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 3 Inline Data
6 The inline data feature was designed to handle the case that a file's
7 data is so tiny that it readily fits inside the inode, which
9 file is smaller than 60 bytes, then the data are stored inline in
12 “system.data” within the inode body (“ibody EA”). This of course
14 If the data size increases beyond i\_block + ibody EA, a regular block
18 inline data, one ought to be able to store 160 bytes of data in a
22 The inline data feature requires the presence of an extended attribute
23 for “system.data”, even if the attribute value is zero length.
30 entries; see ``struct ext4_dir_entry``. If there is a “system.data”
[all …]
|
| /Documentation/i2c/ |
| D | i2c-protocol.rst | 17 Comm (8 bits): Command byte, a data byte which often selects a register on
19 Data (8 bits): A plain data byte. Sometimes, I write DataLow, DataHigh
20 for 16 bit data.
21 Count (8 bits): A data byte containing the length of a block operation.
23 [..]: Data sent by I2C device, as opposed to data sent by the
33 S Addr Wr [A] Data [A] Data [A] ... [A] Data [A] P
41 S Addr Rd [A] [Data] A [Data] A ... A [Data] NA P
53 S Addr Rd [A] [Data] NA S Addr Wr [A] Data [A] P
77 S Addr Rd [A] [Data] NA Data [A] P
83 This is often used to gather transmits from multiple data buffers in
[all …]
|
| D | smbus-protocol.rst | 24 single data byte, the functions using SMBus protocol operation names execute
44 Comm (8 bits): Command byte, a data byte which often selects a register on
46 Data (8 bits): A plain data byte. Sometimes, I write DataLow, DataHigh
47 for 16 bit data.
48 Count (8 bits): A data byte containing the length of a block operation.
50 [..]: Data sent by I2C device, as opposed to data sent by the host
73 S Addr Rd [A] [Data] NA P
86 S Addr Wr [A] Data [A] P
97 S Addr Wr [A] Comm [A] S Addr Rd [A] [Data] NA P
105 This operation is very like Read Byte; again, data is read from a
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | micrel-ksz90x1.txt | 52 - rxd0-skew-ps : Skew control of RX data 0 pad
53 - rxd1-skew-ps : Skew control of RX data 1 pad
54 - rxd2-skew-ps : Skew control of RX data 2 pad
55 - rxd3-skew-ps : Skew control of RX data 3 pad
56 - txd0-skew-ps : Skew control of TX data 0 pad
57 - txd1-skew-ps : Skew control of TX data 1 pad
58 - txd2-skew-ps : Skew control of TX data 2 pad
59 - txd3-skew-ps : Skew control of TX data 3 pad
79 - rxd0-skew-ps : Skew control of RX data 0 pad
80 - rxd1-skew-ps : Skew control of RX data 1 pad
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 6 Video data pipelines usually consist of external devices, e.g. camera sensors,
8 video DMA engines and video data processors.
14 Data interfaces on all video devices are described by their child 'port' nodes.
15 Configuration of a port depends on other devices participating in the data
46 configuration of this device for data exchange with other device. In most
52 where supported by a device. For example, in case where a data interface of
53 a device is partitioned into multiple data busses, e.g. 16-bit input port
55 and data-shift properties can be used to assign physical data lines to each
100 slave device (data source) by the master device (data sink). In the master
101 mode the data source device is also the source of the synchronization signals.
[all …]
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 80 system calls to send data to the kernel or obtain data from the
91 copying of the output data to its final destination can be avoided.
103 filled struct sockaddr data structure. This data structure must be
120 Using the send() system call, the application provides the data that
142 initialization, the struct sockaddr data structure must be filled as
154 Before data can be sent to the kernel using the write/send system call
158 Using the sendmsg() system call, the application provides the data that
160 specified with the data structure provided by the sendmsg() system call.
163 struct cmsghdr data structure. See recv(2) and cmsg(3) for more
164 information on how the cmsghdr data structure is used together with the
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 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.
17 situation the dm-crypt target creates the integrity data and passes them
21 error is returned instead of random data.
25 mode, the dm-integrity target can be used to detect silent data
30 region's data and integrity tags are not synchronized - if the machine
32 is faster than the journal mode, because we don't have to write the data
33 twice, but it is also less reliable, because if data corruption happens
68 not used and data sectors and integrity tags are written
69 separately. In case of crash, it is possible that the data
[all …]
|
| D | persistent-data.rst | 2 Persistent data
10 different targets were rolling their own data structures, for example:
17 Maintaining these data structures takes a lot of work, so if possible
20 The persistent-data library is an attempt to provide a re-usable
29 under drivers/md/persistent-data.
36 This provides access to the data on disk in fixed sized-blocks. There
38 keep data that is being used in the cache.
40 Clients of persistent-data are unlikely to use this directly.
52 ensures that all data is flushed before it writes the superblock.
62 On-disk data structures that keep track of reference counts of blocks.
[all …]
|
| D | verity.rst | 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
43 The block size on a data device in bytes.
50 The number of data blocks on the data device. Additional blocks are
51 inaccessible. You can place hashes to the same partition as data, in this
93 verification fails. Use encoding data from the specified device. This
94 may be the same device where data and hash blocks reside, in which case
95 fec_start must be outside data and hash areas.
97 If the encoding data covers additional metadata, it must be accessible
100 Note: block sizes for data and hash devices must match. Also, if the
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-boot_params | 5 files: "data" and "version" and one subdirectory "setup_data".
12 "data" file is the binary representation of struct boot_params.
17 "setup_data" subdirectory contains the setup_data data
22 files "type" and "data". "type" file is the string
23 representation of setup_data type. "data" file is the binary
28 |__ data
31 | | |__ data
34 | |__ data
|
| /Documentation/driver-api/ |
| D | edid.rst | 15 - The graphics board is unable to detect any EDID data.
16 - The graphics board incorrectly forwards EDID data to the driver.
17 - The monitor sends no or bogus EDID data.
18 - A KVM sends its own EDID data instead of querying the connected monitor.
24 individually prepared or corrected EDID data set in the /lib/firmware
26 (see drivers/gpu/drm/drm_edid_load.c) contains built-in data sets for
29 not contain code to create these data. In order to elucidate the origin
31 individual data for a specific misbehaving monitor, commented sources
34 To create binary EDID and C source code files from the existing data
38 replace the settings with your own data and add a new target to the
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5659.txt | 23 - realtek,dmic1-data-pin
25 1: using IN2N pin as dmic1 data pin
26 2: using GPIO5 pin as dmic1 data pin
27 3: using GPIO9 pin as dmic1 data pin
28 4: using GPIO11 pin as dmic1 data pin
30 - realtek,dmic2-data-pin
32 1: using IN2P pin as dmic2 data pin
33 2: using GPIO6 pin as dmic2 data pin
34 3: using GPIO10 pin as dmic2 data pin
35 4: using GPIO12 pin as dmic2 data pin
|
| D | rt5645.txt | 22 - realtek,dmic1-data-pin
24 1: using IN2P pin as dmic1 data pin
25 2: using GPIO6 pin as dmic1 data pin
26 3: using GPIO10 pin as dmic1 data pin
27 4: using GPIO12 pin as dmic1 data pin
29 - realtek,dmic2-data-pin
31 1: using IN2N pin as dmic2 data pin
32 2: using GPIO5 pin as dmic2 data pin
33 3: using GPIO11 pin as dmic2 data pin
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | lvds.yaml | 15 incompatible data link layers have been used over time to transmit image data
41 data-mapping:
49 LVDS data mappings are defined as follows.
51 - "jeida-18" - 18-bit data mapping compatible with the [JEIDA], [LDI] and
52 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
62 - "jeida-24" - 24-bit data mapping compatible with the [DSIM] and [LDI]
63 specifications. Data are transferred as follows on 4 LVDS lanes.
74 - "vesa-24" - 24-bit data mapping compatible with the [VESA] specification.
75 Data are transferred as follows on 4 LVDS lanes.
90 CTL2: Data Enable
[all …]
|
| /Documentation/devicetree/ |
| D | of_unittest.txt | 8 This document explains how the test data required for executing OF unittest
19 from the unflattened device tree data structure. This interface is used by
23 2. Test-data
25 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
26 the test data required for executing the unit tests automated in
30 drivers/of/unittest-data/tests-interrupts.dtsi
31 drivers/of/unittest-data/tests-platform.dtsi
32 drivers/of/unittest-data/tests-phandle.dtsi
33 drivers/of/unittest-data/tests-match.dtsi
53 2.1. Adding the test data
[all …]
|
| /Documentation/ |
| D | kref.txt | 22 To use a kref, add one to your data structures like::
33 The kref can occur anywhere within the data structure.
41 struct my_data *data;
43 data = kmalloc(sizeof(*data), GFP_KERNEL);
44 if (!data)
46 kref_init(&data->refcount);
60 kref_get(&data->refcount);
67 kref_put(&data->refcount, data_release);
80 For example, if you allocate some data and then pass it to another
85 struct my_data *data = container_of(ref, struct my_data, refcount);
[all …]
|
| /Documentation/networking/ |
| D | net_dim.txt | 31 runtime data sampled from the system. Net DIM is such a mechanism. In each
32 iteration of the algorithm, it analyses a given sample of the data, compares it
34 interrupt moderation configuration fields. The data sample is composed of data
36 samples is also measured. Net DIM compares the current and the previous data and
48 1. Calculates new data sample.
53 The first two steps are straightforward, both the new and the previous data are
54 supplied by the driver registered to Net DIM. The previous data is the new data
56 between the new and previous data and decides on the result of the last step.
66 assumes the data provided by the driver is valid.
85 would have trouble making the correct decisions if the wrong data is supplied to
[all …]
|
| D | tls.rst | 11 TCP. TLS provides end-to-end data integrity and confidentiality.
29 data-path to the kernel. There is a separate socket option for moving
64 Sending TLS application data
67 After setting the TLS_TX socket option all application data sent over this
76 send() data is directly encrypted from the userspace buffer provided
79 The sendfile system call will send the file's data over TLS records of maximum
92 The kernel will need to allocate a buffer for the encrypted data.
96 -ENOMEM and some data was left on the socket buffer from a previous
97 call using MSG_MORE, the MSG_MORE data is left on the socket buffer.
99 Receiving TLS application data
[all …]
|
| /Documentation/scsi/ |
| D | cxgb3i.txt | 7 series of products) support iSCSI acceleration and iSCSI Direct Data Placement
15 Data digest into the PDUs.
17 Data digest of the PDUs.
19 - Direct Data Placement (DDP)
21 S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
23 on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
24 in Data-Out PDUs.
28 On transmitting, S3 h/w accepts the complete PDU (header + data)
35 segments, separating the header and data, calculating and verifying
36 the digests, then forwarding the header to the host. The payload data,
[all …]
|
| /Documentation/admin-guide/auxdisplay/ |
| D | cfag12864b.rst | 40 :Data size: 1 byte each address
56 Data 0 ( 2)------------------------------( 4) Data 0
57 Data 1 ( 3)------------------------------( 5) Data 1
58 Data 2 ( 4)------------------------------( 6) Data 2
59 Data 3 ( 5)------------------------------( 7) Data 3
60 Data 4 ( 6)------------------------------( 8) Data 4
61 Data 5 ( 7)------------------------------( 9) Data 5
62 Data 6 ( 8)------------------------------(10) Data 6
63 Data 7 ( 9)------------------------------(11) Data 7
71 Select (17)------------------------------(16) Data / Instruction
|
| /Documentation/media/uapi/v4l/ |
| D | dev-rds.rst | 16 The Radio Data System transmits supplementary information in binary
48 driver only passes RDS blocks without interpreting the data the
50 :ref:`Reading RDS data <reading-rds-data>`. For future use the flag
59 ``V4L2_TUNER_SUB_RDS`` will be set if RDS data was detected.
71 blocks without interpreting the data the ``V4L2_TUNER_CAP_RDS_BLOCK_IO``
75 :ref:`Writing RDS data <writing-rds-data>` and
79 .. _reading-rds-data:
81 Reading RDS data
84 RDS data can be read from the radio device with the
85 :ref:`read() <func-read>` function. The data is packed in groups of
[all …]
|
| D | dev-sliced-vbi.rst | 13 Sliced VBI Data Interface
21 Sliced VBI devices use hardware to demodulate data transmitted in the
23 :ref:`raw VBI interface <raw-vbi>`. The data is passed as short
34 Different file descriptors must be used to pass raw and sliced VBI data
65 To find out which data services are supported by the hardware
154 Applications initialize this array with sets of data services the
162 Data services are defined in :ref:`vbi-services2`. Array indices
208 array (that is the number of lines potentially carrying data).
286 read or write data without prior format negotiation, after switching the
297 Reading and writing sliced VBI data
[all …]
|
| /Documentation/networking/device_drivers/qualcomm/ |
| D | rmnet.txt | 11 handle multiple private data networks (PDN) like a default internet, tethering,
16 Aggregation is required to achieve high data rates. This involves hardware
22 a. MAP packet (data / control)
29 Function Command / Data Reserved Pad Multiplexer ID Payload length
33 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
34 or data packet. Control packet is used for transport level flow control. Data
42 Multiplexer ID is to indicate the PDN on which data has to be sent.
56 Function Command data
68 Aggregation is multiple MAP packets (can be data or command) delivered to
|
12345678910>>...68