Searched full:bytes (Results 1 – 25 of 741) sorted by relevance
12345678910>>...30
| /Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 29 ALGN(n) means padding with null bytes to an n-byte boundary
44 formats); arbitrary amounts zero bytes (for padding) can be added
58 c_magic 6 bytes The string "070701" or "070702"
59 c_ino 8 bytes File inode number
60 c_mode 8 bytes File mode and permissions
61 c_uid 8 bytes File uid
62 c_gid 8 bytes File gid
63 c_nlink 8 bytes Number of links
64 c_mtime 8 bytes Modification time
65 c_filesize 8 bytes Size of data field
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | reexport.rst | 38 bytes, rounded up to the nearest multiple of four bytes.
43 | NFSv2 | 32 bytes |
45 | NFSv3 | 64 bytes |
47 | NFSv4 | 128 bytes |
52 bytes--which is unlikely.
65 | ext4: | 28 bytes | 52 bytes |
67 | xfs: | 32 bytes | 56 bytes |
69 | btrfs: | 40 bytes | 64 bytes |
79 requires another 4 to 8 bytes in the filehandle.
82 bytes.
[all …]
|
| /Documentation/networking/ |
| D | udplite.rst | 70 sets the checksum coverage length to 20 bytes (12b data + 8b header).
71 Of each packet only the first 20 bytes (plus the pseudo-header) will be
179 Payload: 1536 bytes Send Buffer: 1024 bytes
180 MTU: 1500 bytes Coverage Length: 856 bytes
182 UDP-Lite will ship the 1536 bytes in two separate packets::
184 Packet 1: 1024 payload + 8 byte header + 20 byte IP header = 1052 bytes
185 Packet 2: 512 payload + 8 byte header + 20 byte IP header = 540 bytes
187 The coverage packet covers the UDP-Lite header and 848 bytes of the
196 Payload: 1024 bytes Send buffer size: 1024 bytes
197 MTU: 300 bytes Coverage length: 575 bytes
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-wilco-ec | 21 bytes will be sent to the EC. Then, you can read the bytes of
24 For writing, bytes 0-1 indicate the message type, one of enum
26 request, starting at MBOX[0]. At least three bytes are required
42 Note that the first 16 bytes of the received MBOX[] will be
43 printed, even if some of the data is junk, and skipping bytes
44 17 to 32. It is up to you to know how many of the first bytes of
|
| D | sysfs-bus-iio-dma-buffer | 9 This property reports the alignment requirements in bytes.
10 This means that the buffer size in bytes needs to be a integer
14 on the enabled channels and the bytes per channel. This means
17 the alignment requirement reported in bytes by this property
|
| D | sysfs-class-bsr | 8 register in bytes.
16 (RO) The length of memory region that can be mapped in bytes.
24 (RO) The stride or the interval at which the allocated BSR bytes
|
| D | debugfs-pfo-nx-crypto | 29 The total number of bytes encrypted using AES in any of the driver's
36 The total number of bytes hashed by the hardware using SHA-256.
42 The total number of bytes hashed by the hardware using SHA-512.
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-howto.rst | 215 READ ( 1 bytes): OKAY
216 READ ( 1024 bytes): OKAY
217 READ ( 1025 bytes): OKAY
218 READ (1024000 bytes): OKAY
219 READ (1024001 bytes): OKAY
223 WRITE ( 1 bytes): OKAY
224 WRITE ( 1024 bytes): OKAY
225 WRITE ( 1025 bytes): OKAY
226 WRITE (1024000 bytes): OKAY
227 WRITE (1024001 bytes): OKAY
[all …]
|
| /Documentation/w1/slaves/ |
| D | w1_ds2423.rst | 26 Each lines will contain the values of 42 bytes read from the counter and
32 Meaning of 42 bytes represented is following:
35 - 4 bytes for the counter value
36 - 4 zero bytes
37 - 2 bytes for crc16 which was calculated from the data read since the previous crc bytes
38 - 31 remaining bytes from the ram page
|
| D | w1_ds2438.rst | 19 a battery pack. It also has a 40 bytes of nonvolatile EEPROM.
41 This file provides full 8 bytes of the chip Page 0 (00h).
44 from the slave device. If it is correct, the 8 bytes page data are passed
49 This file provides full 8 bytes of the chip Page 1 (01h).
52 from the slave device. If it is correct, the 8 bytes page data are passed
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 66 The encryption key size in bytes. The kernel key payload size must match
137 integrity:<bytes>:<type>
138 The device requires additional <bytes> metadata per-sector stored
149 sector_size:<bytes>
150 Use <bytes> as the encryption unit instead of 512 bytes sectors.
151 This option can be in range 512 - 4096 bytes and must be power of two.
156 instead of default 512 bytes sectors.
158 For example, if <sector_size> is 4096 bytes, plain64 IV for the second
160 The <iv_offset> must be multiple of <sector_size> (in 512 bytes units)
163 integrity_key_size:<bytes>
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 5 profile will be read next. The data has to be 3 bytes long.
17 The data has to be 3 bytes long.
26 The data has to be 125 bytes long.
36 in written data. The data has to be 95 bytes long.
46 written data. The data has to be 35 bytes long.
56 in written data. The data has to be 23 bytes long.
66 is included in written data. The data has to be 8 bytes long.
76 in written data. The data has to be 294 bytes long.
87 written data. The data has to be 6 bytes long.
98 The data has to be 16 bytes long.
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 16 The data is 6 bytes long.
26 written data. The data has to be 6 bytes long.
36 in written data. The data has to be 6 bytes long.
46 in written data. The data has to be 65 bytes long.
56 in written data. The data has to be 41 bytes long.
66 written data. The data has to be 35 bytes long.
76 written data. The data has to be 29 bytes long.
86 in written data. The data has to be 23 bytes long.
96 The data has to be 20 bytes long.
104 The data has to be 10 bytes long for Isku, IskuFX needs 16 bytes
[all …]
|
| D | sysfs-driver-hid-roccat-konepure | 9 The data has to be 3 bytes long.
17 profile will be read next. The data has to be 3 bytes long.
26 The data is 6 bytes long.
36 included in written data. The data has to be 2082 bytes long.
47 buttons back to the mouse. The data has to be 59 bytes long.
63 settings back to the mouse. The data has to be 31 bytes long.
76 set. The data has to be 6 bytes long.
84 The data has to be 16 bytes long.
94 The data has to be 4 bytes long.
103 The returned data is 1028 bytes in size.
|
| D | sysfs-driver-hid-roccat-savu | 9 47 bytes long.
21 profile will be read next. The data has to be 3 bytes long.
33 settings back to the mouse. The data has to be 43 bytes long.
45 The data is 8 bytes long.
54 The data has to be 2083 bytes long.
67 The data has to be 3 bytes long.
76 The data has to be 4 bytes long.
|
| /Documentation/filesystems/ |
| D | romfs.rst | 15 defunct) filesystems, compiled as module need more than 20000 bytes,
16 while romfs is less than a page, about 4000 bytes (assuming i586
52 is 32 bytes (this is an empty file, with a less than 16 character
55 bytes. This is quite rare however, since most file names are longer
56 than 3 bytes, and shorter than 15 bytes.
64 +---+---+---+---+ The ASCII representation of those bytes
67 8 | full size | The number of accessible bytes in this fs.
69 12 | checksum | The checksum of the FIRST 512 BYTES.
80 The first eight bytes identify the filesystem, even for the casual
82 bytes accessible from the start of this filesystem. The 4th longword
[all …]
|
| /Documentation/staging/ |
| D | lzo.rst | 27 - a length (number of bytes to copy from dictionary)
35 The first byte of the block follows a different encoding from other bytes, it
41 length, up to 255 may be added in increments by consuming more bytes with a
48 length += 255*(number of zero bytes)
56 Certain encodings involve one extra byte, others involve two extra bytes
70 for the distance, thus requiring 3 bytes.
75 are called under the assumption that a certain number of bytes follow
77 They just have to "refill" this credit if they consume extra bytes. This
106 stream length is at least 5 bytes (length of shortest possible
136 bytes to encode a copy of 2 other bytes but it encodes the number of
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 9 file is smaller than 60 bytes, then the data are stored inline in
18 inline data, one ought to be able to store 160 bytes of data in a
20 that, the limit was 156 bytes due to inefficient use of inode space.
28 The first four bytes of i_block are the inode number of the parent
|
| D | ifork.rst | 6 Depending on the type of file an inode describes, the 60 bytes of
15 string is less than 60 bytes long. Otherwise, either extents or block
68 which is 12 bytes long:
104 recorded as ``struct ext4_extent_idx``, and are 12 bytes long:
134 and are also 12 bytes long:
166 extent entries always left at least 4 bytes of unallocated space at the
174 ``struct ext4_extent_tail`` is 4 bytes long:
193 set for the inode, it is possible that the first 60 bytes of the file
|
| /Documentation/i2c/busses/ |
| D | i2c-mlxcpld.rst | 45 Number of data bytes to write in read transaction
47 Number of address bytes to write in read transaction.
51 DATAx 0xa - 0x54 - 68 bytes data buffer regs.
52 For write transaction address is specified in four first bytes
55 specified in the four first bytes (DATA0 - DATA3). Data is read
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 123 …CCBs are either 64 or 128 bytes long, depending on the operation type. The exact contents of the C…
203 … Long CCB flag indicates whether the submitted CCB is 64 or 128 bytes long; value is 0 for 64 bytes
204 and 1 for 128 bytes.
231 …The input of the target CCB must start within 64 bytes of the output of the source CCB or the pipe…
256 0x0 Fixed width byte packed Up to 16 bytes
262 … 0x4 Fixed width byte packed with run Up to 16 bytes; data stream of run lengths must be
268 … 0x8 Fixed width byte packed with Up to 16 bytes before the encoding; compressed stream
276 … 0xA Variable width byte packed with Up to 16 bytes before the encoding; compressed stream
288 …0xC Fixed width byte packed with Up to 16 bytes before the encoding; compressed str…
299 If OZIP encoding is used, there must be no reserved bytes in the table.
[all …]
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 40 Function Raw bytes
48 Padding is the number of bytes to be appended to the payload to
66 Function Raw bytes Checksum offload header
74 Padding is the number of bytes to be appended to the payload to
98 Padding is the number of bytes to be appended to the payload to
101 Checksum start offset, Indicates the offset in bytes from the beginning of the
104 Checksum length is the Length in bytes starting from CKSUM_START_OFFSET,
119 Function Raw bytes
128 Padding is the number of bytes to be appended to the payload to
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 149 - The number of bytes received on ring i.
157 - The number of bytes transmitted on ring i.
177 - The number of TSO bytes transmitted on ring i [#accel]_.
186 - The number of TSO bytes which are indicated to be carry internal
197 - Number of received bytes processed using hardware-accelerated GRO. The
198 number of hardware GRO offloaded bytes received on ring i. Only true GRO
217 - Number of bytes for header only packets in header/data split mode
230 - Number of bytes for packets that were not split in header/data split
242 - The number of LRO bytes received on ring i [#accel]_.
285 - Number of received packets that need padding larger than eight bytes for
[all …]
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 367 Hardware ECC generator providing 3 bytes ECC per 256 byte.
371 Hardware ECC generator providing 3 bytes ECC per 512 byte.
375 Hardware ECC generator providing 6 bytes ECC per 512 byte.
379 Hardware ECC generator providing 8 bytes ECC per 512 byte.
417 The ECC bytes must be placed immediately after the data bytes in order
421 remaining free bytes in the oob area are managed by the autoplacement
578 is stored in 4 consecutive bytes in the spare area of the device. The
641 The eccbytes member defines the number of ecc bytes per page.
653 length in bytes. More than one area can be defined. The list is
681 Automatic placement uses the built in defaults to place the ecc bytes in
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-read.rst | 34 Max number of bytes to read
39 :c:func:`read()` attempts to read up to ``count`` bytes from file
62 On success, the number of bytes read is returned. It is not an error if
63 this number is smaller than the number of bytes requested, or the amount
|
12345678910>>...30