Searched full:header (Results 1 – 25 of 696) sorted by relevance
12345678910>>...28
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 20 name: header-flags
50 name: header
61 enum: header-flags
148 name: header
150 nested-attributes: header
163 name: header
165 nested-attributes: header
175 name: header
177 nested-attributes: header
252 name: header
[all …]
|
| D | nftables.yaml | 1152 fixed-header: nfgenmsg
1166 fixed-header: nfgenmsg
1176 fixed-header: nfgenmsg
1186 fixed-header: nfgenmsg
1200 fixed-header: nfgenmsg
1210 fixed-header: nfgenmsg
1220 fixed-header: nfgenmsg
1230 fixed-header: nfgenmsg
1244 fixed-header: nfgenmsg
1254 fixed-header: nfgenmsg
[all …]
|
| /Documentation/arch/riscv/ |
| D | boot-image-header.rst | 2 Boot image header in RISC-V Linux
8 This document only describes the boot image header details for RISC-V Linux.
10 The following 64-byte header is present in decompressed Linux kernel image::
17 u32 version; /* Version of this header */
24 This header format is compliant with PE/COFF header and largely inspired from
25 ARM64 header. Thus, both ARM64 & RISC-V header can be combined into one common
26 header in future.
31 - This header is also reused to support EFI stub for RISC-V. EFI specification
32 needs PE/COFF image header in the beginning of the kernel image in order to
35 PE/COFF header.
[all …]
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 21 routes to the appropriate PDN after removing the MAP header.
32 MAP header fields are in big endian format.
53 Payload length includes the padding length but does not include MAP header
58 MAP header fields are in big endian format.
66 Function Raw bytes Checksum offload header
79 Payload length includes the padding length but does not include MAP header
82 Checksum offload header, has the information about the checksum processing done
83 by the hardware.Checksum offload header fields are in big endian format.
102 IP header, from which modem computed checksum.
111 MAP header fields are in big endian format.
[all …]
|
| /Documentation/userspace-api/ |
| D | ELF.rst | 10 "First" program header is the one with the smallest offset in the file:
13 "Last" program header is the one with the biggest offset in the file:
19 First PT_INTERP program header is used to locate the filename of ELF
25 Last PT_GNU_STACK program header defines userspace stack executability
31 ELF interpreter's last PT_GNU_PROPERTY program header is used (since
33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-uvc.rst | 9 UVC Payload Header Data
17 exact copies of the standard part of UVC Payload Header contents and auxiliary
22 Each UVC payload header can be between 2 and 12 bytes large. Buffers can
26 SCR field or with that field identical to the previous header), or generally to
33 :header-rows: 1
45 * - :cspan:`1` *The rest is an exact copy of the UVC payload header:*
51 - The rest of the header, possibly including UVC PTS and SCR fields
|
| D | ext-ctrls-codec-stateless.rst | 44 :header-rows: 0
114 :header-rows: 0
144 :header-rows: 0
187 :header-rows: 0
242 :header-rows: 0
293 :header-rows: 0
315 :ref:`h264`, section 7.4.3 "Slice Header Semantics". For further
328 :header-rows: 0
397 :header-rows: 0
412 under the conditions explained in section 7.3.3 "Slice header
[all …]
|
| D | ext-ctrls-codec.rst | 49 :header-rows: 0
104 :header-rows: 0
127 :header-rows: 0
151 :header-rows: 0
178 :header-rows: 0
223 :header-rows: 0
268 :header-rows: 0
316 :header-rows: 0
371 :header-rows: 0
398 :header-rows: 0
[all …]
|
| /Documentation/trace/ |
| D | hisi-ptt.rst | 214 - 4'b0000: 4DW length per TLP header
215 - 4'b0001: 8DW length per TLP header
217 The traced TLP header format is different from the PCIe standard.
219 When using the 8DW data format, the entire TLP header is logged
220 (Header DW0-3 shown below). For example, the TLP header for Memory
222 the header for Configuration Requests is shown in Figure 2.20, etc.
236 DW2 [ Header DW0 ]
237 DW3 [ Header DW1 ]
238 DW4 [ Header DW2 ]
239 DW5 [ Header DW3 ]
[all …]
|
| /Documentation/networking/ |
| D | segmentation-offloads.rst | 38 the network and transport header offsets of the skbuff so that the device
39 drivers will be able determine the offsets of the IP or IPv6 header and the
40 TCP header. In addition as CHECKSUM_PARTIAL is required csum_start should
41 also point to the TCP header of the packet.
75 from the standard list of headers to "inner" header offsets.
98 fact that the outer header also requests to have a non-zero checksum
99 included in the outer header.
102 header has requested a remote checksum offload. In this case the inner
103 headers will be left with a partial checksum and only the outer header
128 this is IPv4 ID in the case that the DF bit is set for a given IP header.
[all …]
|
| D | radiotap-headers.rst | 18 Structure of the header
24 the header for argument index 0 (IEEE80211_RADIOTAP_TSFT) is present in the
46 After the fixed part of the header, the arguments follow for each argument
62 the first byte of the radiotap header. The absolute alignment of that first
63 byte isn't defined. So even if the whole radiotap header is starting at, eg,
64 address 0x00000003, still the first byte of the radiotap header is treated as
68 entities in the fixed radiotap header or the argument region means that you
81 Example valid radiotap header
87 0x0b, 0x00, // <- radiotap header length
103 /* buf points to the start of the radiotap header part */
[all …]
|
| D | mpls-sysctl.rst | 31 Control whether TTL is propagated from the IPv4/IPv6 header to
32 the MPLS header on imposing labels and propagated from the
33 MPLS header to the IPv4/IPv6 header on popping the last label.
43 propagated from an IP header, either because one isn't present
|
| D | checksum-offloads.rst | 41 pseudo-header for UDP or TCP).
45 different header layers, and the rest will have to be handled by another
52 No offloading of the IP header checksum is performed; it is always done in
53 software. This is OK because when we build the IP header, we obviously have it
88 to the complement of the sum of the pseudo header, because everything else gets
107 LCO is performed by the stack when constructing an outer UDP header for an
111 It is also performed when constructing an IPv4 GRE header, in
113 constructing an IPv6 GRE header; the GRE checksum is computed over the whole
121 encapsulation layer will sum over both its own header and the 'middle' header.
122 This does mean that the 'middle' header will get summed multiple times, but
|
| D | udplite.rst | 38 length (default = header length = 8). Details are in the next section.
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
73 base header.
94 3. Header Files
97 The socket API requires support through header files in /usr/include:
103 for UDP-Lite header fields and protocol constants
105 For testing purposes, the following can serve as a ``mini`` header file::
112 Ready-made header files for various distros are in the UDP-Lite tarball.
174 first one contains the L4 header.
[all …]
|
| /Documentation/kbuild/ |
| D | headers_install.rst | 5 The "make headers_install" command exports the kernel's header files in a
8 The linux kernel's exported header files describe the API for user space
9 programs attempting to use kernel services. These kernel header files are
12 system calls. The C library's header files include the kernel header files
43 The kernel header export infrastructure is maintained by David Woodhouse
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 11 (2) the header of a swap file is not in the first block of the partition that
16 In principle the location of a swap file's header may be determined with the
22 header is located. For convenience, this offset is expressed in <PAGE_SIZE>
34 FIBMAP ioctl and determine the location of the file's swap header, as the
43 and <swap_file_offset> is the offset of the swap header determined by the
45 by the same application that determines the swap file's header offset using the
61 the location of its header need not be the same as before. Thus every time
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 38 :header-rows: 1
70 :header-rows: 1
103 :header-rows: 1
133 :header-rows: 1
159 :header-rows: 1
241 :header-rows: 1
312 - Maximum number of dx_entries that can follow this header, plus 1 for
313 the header itself.
317 - Actual number of dx_entries that follow this header, plus 1 for the
318 header itself.
[all …]
|
| D | ifork.rst | 58 (``eh.eh_depth`` > 0), the header is followed by ``eh.eh_entries``
61 is a leaf node (``eh.eh_depth == 0``), then the header is followed by
67 The extent tree header is recorded in ``struct ext4_extent_header``,
72 :header-rows: 1
85 - Number of valid entries following the header.
89 - Maximum number of entries that could follow the header.
108 :header-rows: 1
138 :header-rows: 1
165 Prior to the introduction of metadata checksums, the extent header +
178 :header-rows: 1
|
| D | journal.rst | 63 :header-rows: 1
91 :header-rows: 1
105 Block Header
108 Every block in the journal starts with a common 12-byte header
113 :header-rows: 1
139 :header-rows: 1
169 :header-rows: 1
182 - Common header identifying this as a superblock.
288 :header-rows: 1
302 :header-rows: 1
[all …]
|
| /Documentation/driver-api/pldmfw/ |
| D | file-format.rst | 7 A PLDM firmware package is a binary file which contains a header that
9 package header, one or more firmware records, and one or more components
17 | Package Header |
29 | Package Header CRC |
49 Package Header
52 The package header begins with the UUID of the PLDM file format, and
54 also includes the total header size, a release date, the size of the
57 The following diagram provides an overview of the package header::
59 header layout
65 | Header Size |
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 198 routed and their IP header is corrupted: wrong checksum, wrong IP version
199 or too short Internet Header Length (IHL)
244 bits set in VXLAN header)
389 option in their Hop-by-Hop extension header. Such packets need to be
414 - Traps packets dropped due to an error in the VXLAN header parsing which
418 - Traps packets dropped due to an error in the LLC+SNAP header parsing
421 - Traps packets dropped due to an error in the VLAN header parsing. Could
425 - Traps packets dropped due to an error in the PPPoE+PPP header parsing.
428 any common error on this type of header
431 - Traps packets dropped due to an error in the MPLS header parsing which
[all …]
|
| /Documentation/arch/loongarch/ |
| D | booting.rst | 27 Header of Linux/LoongArch kernel images
31 a 64-byte header structured like::
33 u32 MZ_MAGIC /* "MZ", MS-DOS header */
42 u32 pe_header - _head /* Offset to the PE header */
|
| /Documentation/filesystems/ |
| D | omfs.rst | 49 and extents. Each sysblock has a header containing CRCs of the entire
55 Sysblock header information::
59 __be32 h_body_size; /* size of useful data after header */
65 u8 h_check_xor; /* XOR of header bytes before this */
72 struct omfs_header i_head; /* header */
111 e_next. These have a header but lack the rest of the inode structure.
|
| /Documentation/scsi/ |
| D | scsi-parameters.rst | 20 See header of drivers/scsi/advansys.c.
44 See header of drivers/scsi/ips.c.
58 See header of drivers/scsi/NCR_D700.c.
102 See header of drivers/scsi/sim710.c.
108 See header of drivers/scsi/wd33c93.c.
|
| D | cxgb3i.rst | 18 On transmitting, Chelsio S3 h/w computes and inserts the Header and
20 On receiving, Chelsio S3 h/w computes and verifies the Header and
32 On transmitting, S3 h/w accepts the complete PDU (header + data)
39 segments, separating the header and data, calculating and verifying
40 the digests, then forwarding the header to the host. The payload data,
|
12345678910>>...28