Searched full:packet (Results 1 – 25 of 315) sorted by relevance
12345678910>>...13
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 63 Lower-level packet transport is implemented in the *packet transport layer
66 the packet transport logic and handles things like packet validation, packet
67 acknowledgment (ACKing), packet (retransmission) timeouts, and relaying
68 packet payloads to higher-level layers.
71 around command-type packet payloads, i.e. requests (sent from host to EC),
97 Packet Transport Layer
100 The packet transport layer is represented via |ssh_ptl| and is structured
107 managed by the packet transport layer, which is essentially the lowest layer
113 This structure contains the required fields to manage the packet inside the
118 counter reaches zero, the ``release()`` callback provided to the packet via
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 20 packet with a TTL of 1. Upon routing the packet the device must send it to the
26 is called "packet trapping".
32 supported packet traps with ``devlink`` and report trapped packets to
36 bytes accounting and potentially report the packet to user space via a netlink
39 as it allows users to obtain further visibility into packet drops that would
44 Netlink event: Packet w/ metadata
76 | Trapped packet
89 The ``devlink-trap`` mechanism supports the following packet trap types:
112 The ``devlink-trap`` mechanism supports the following packet trap actions:
114 * ``trap``: The sole copy of the packet is sent to the CPU.
[all …]
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 27 2. Packet format
30 a. MAP packet v1 (data / control)
34 Packet format::
42 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
43 or data packet. Command packet is used for transport level flow control. Data
56 b. Map packet v4 (data / control)
60 Packet format::
68 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
69 or data packet. Command packet is used for transport level flow control. Data
85 Packet format::
[all …]
|
| /Documentation/networking/ |
| D | ipsec.rst | 12 Small IP packet won't get compressed at sender, and failed on
36 when sending non-compressed packet to the peer (whether or not packet len
38 packet len), the packet is dropped when checking the policy as this packet
40 security path. Such naked packet will not eventually make it to upper layer.
45 above scenario. The consequence of doing so is small packet(uncompressed)
|
| D | xfrm_device.rst | 27 * IPsec packet offload:
45 and for packet offload
51 offload packet dev eth4 dir in
53 ip x p add src 14.0.0.70 dst 14.0.0.52 offload packet dev eth4 dir in
67 /* Crypto and Packet offload callbacks */
76 /* Solely packet offload callbacks */
114 not applicable for packet offload mode
124 When the network stack is preparing an IPsec packet for an SA that has
127 will serviceable. This can check the packet information to be sure the
132 When ready to send, the driver needs to inspect the Tx packet for the
[all …]
|
| D | snmp_counter.rst | 21 IpExtInOctets. It will be increased even if the packet is dropped
64 for the same packet, you might find that IpInReceives count 1, but
69 Defined in `RFC1213 ipInHdrErrors`_. It indicates the packet is
85 This counter means the packet is dropped when the IP stack receives a
86 packet and can't find a route for it from the route table. It might
95 raw socket, kernel will always deliver the packet to the raw socket
102 For IPv4 packet, it means the actual data size is smaller than the
107 Defined in `RFC1213 ipInDiscards`_. It indicates the packet is dropped
115 Defined in `RFC1213 ipOutDiscards`_. It indicates the packet is
122 Defined in `RFC1213 ipOutNoRoutes`_. It indicates the packet is
[all …]
|
| D | openvswitch.rst | 8 flow-level packet processing on selected network devices. It can be
17 on packet headers and metadata to sets of actions. The most common
18 action forwards the packet to another vport; other actions are also
21 When a packet arrives on a vport, the kernel module processes it by
24 no match, it queues the packet to userspace for processing (as part of
42 kernel module passes a packet to userspace, it also passes along the
43 flow key that it parsed from the packet. Userspace then extracts its
44 own notion of a flow key from the packet and compares it against the
47 - If userspace's notion of the flow key for the packet matches the
60 forward the packet manually, without setting up a flow in the
[all …]
|
| D | tc-actions-env-rules.rst | 10 1) If you stealeth or borroweth any packet thou shalt be branching
13 For example if your action queues a packet to be processed later,
14 or intentionally branches by redirecting a packet, then you need to
15 clone the packet.
17 2) If you munge any packet thou shalt call pskb_expand_head in the case
|
| D | x25-iface.rst | 10 This is a description of the messages to be passed between the X.25 Packet
12 setting of the LAPB mode from within the Packet Layer.
18 needs to be passed to and from the Packet Layer for proper operation.
25 Packet Layer to Device Driver
49 Device Driver to Packet Layer
76 Packet Layer and the device driver.
79 the device driver to the Packet Layer, the device driver should not
|
| D | scaling.rst | 18 - RPS: Receive Packet Steering
21 - XPS: Transmit Packet Steering
30 applying a filter to each packet that assigns it to one of a small number
40 IP addresses and TCP ports of a packet. The most common hardware
42 stores a queue number. The receive queue for a packet is determined
44 packet (usually a Toeplitz hash), taking this number as a key into the
96 an IRQ may be handled on any CPU. Because a non-negligible part of packet
166 RPS: Receive Packet Steering
169 Receive Packet Steering (RPS) is logically a software implementation of
173 above the interrupt handler. This is accomplished by placing the packet
[all …]
|
| D | udplite.rst | 71 Of each packet only the first 20 bytes (plus the pseudo-header) will be
124 assumes full coverage, transmits a packet with coverage length of 0
127 if the specified coverage length exceeds the packet length, the packet
134 always wants the whole of the packet covered. In this case, all
173 UDP-Lite packet is split into several IP packets, of which only the
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
188 payload in the first packet, the second packet is fully covered. Note
189 that for the second packet, the coverage length exceeds the packet
[all …]
|
| D | tls-offload.rst | 24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
25 on a packet by packet basis, provided the packets arrive in order.
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
48 for crypto offload based on the socket the packet is attached to,
161 once the packet reaches the device.
165 and hands them to the device. The device identifies the packet as requiring
173 Before a packet is DMAed to the host (but after NIC's embedded switching
174 and packet transformation functions) the device validates the Layer 4
175 checksum and performs a 5-tuple lookup to find any TLS connection the packet
180 decryption, authentication for each record in the packet). The device leaves
[all …]
|
| D | timestamping.rst | 14 Generates a timestamp for each incoming packet in (not necessarily
34 reading the looped packet receive timestamp.
106 are generated just after a device driver hands a packet to the
116 prior to, passing the packet to the network interface. Hence, they
121 Request tx timestamps prior to entering the packet scheduler. Kernel
128 machines with virtual devices where a transmitted packet travels
129 through multiple devices and, hence, multiple packet schedulers,
171 Generate a unique identifier along with each packet. A process can
173 can be reordered in the transmit path, for instance in the packet
179 This option associates each packet at send() with a unique
[all …]
|
| /Documentation/input/devices/ |
| D | elantech.rst | 20 4.2 Native relative mode 4 byte packet format
21 4.3 Native absolute mode 4 byte packet format
24 5.2 Native absolute mode 6 byte packet format
25 5.2.1 Parity checking and packet re-synchronization
30 6.2 Native absolute mode 6 byte packet format
35 7.2 Native absolute mode 6 byte packet format
36 7.2.1 Status packet
37 7.2.2 Head packet
38 7.2.3 Motion packet
41 8.2 Native relative mode 6 byte packet format
[all …]
|
| D | alps.rst | 79 Packet Format
89 PS/2 packet format
134 Dualpoint device -- interleaved packet format
151 touchpad, switching to the interleaved packet format when both the stick and
157 ALPS protocol version 3 has three different packet formats. The first two are
161 The first type is the touchpad position packet::
170 Note that for some devices the trackstick buttons are reported in this packet,
173 The second packet type contains bitmaps representing the x and y axes. In the
175 given axis. Thus the bitmap packet can be used for low-resolution multi-touch
176 data, although finger tracking is not possible. This packet also encodes the
[all …]
|
| D | sentelic.rst | 26 Packet 1
58 Packet 1
86 so we have PACKET NUMBER to identify packets.
88 If PACKET NUMBER is 0, the packet is Packet 1.
89 If PACKET NUMBER is 1, the packet is Packet 2.
92 MSID6 special packet will be enable at the same time when enable MSID 7.
102 Packet 1 (ABSOLUTE POSITION)
108 Byte 1: Bit7~Bit6 => 00, Normal data packet
109 => 01, Absolute coordination packet
110 => 10, Notify packet
[all …]
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 45 the packet data that the BPF program will operate on. The kernel will then
62 The live packet mode is optimised for high performance execution of the supplied
69 operation indicated by the program's return code (drop the packet, redirect
75 in packet processing, like a failure to redirect to a given interface,
81 packet arrived on this interface; i.e., the ``ingress_ifindex`` of the context
83 ``XDP_PASS``, the packet will be injected into the kernel networking stack as
84 though it arrived on that ifindex, and if it returns ``XDP_TX``, the packet
96 separate copy of the packet data. For each repetition, if the program drops
97 the packet, the data page is immediately recycled (see below). Otherwise, the
98 packet is buffered until the end of the batch, at which point all packets
[all …]
|
| D | linux-notes.rst | 45 Legacy BPF Packet access instructions
49 <instruction-set.html#legacy-bpf-packet-access-instructions>`_,
50 Linux has special eBPF instructions for access to packet data that have been
57 These instructions are used to access packet data and can only be used when
58 the program context is a pointer to a networking packet. ``BPF_ABS``
59 accesses packet data at an absolute offset specified by the immediate data
60 and ``BPF_IND`` access packet data at an offset that includes the value of
68 the packet.
73 eBPF program attempts access data beyond the packet boundary, the
|
| D | prog_sk_lookup.rst | 8 into the socket lookup performed by the transport layer when a packet is to be
12 incoming packet by calling the ``bpf_sk_assign()`` BPF helper function.
47 find a listening (TCP) or an unconnected (UDP) socket for an incoming packet.
56 packet.
58 A BPF sk_lookup program can also select a socket to receive the packet by
81 receives information about the packet that triggered the socket lookup. Namely:
|
| /Documentation/netlabel/ |
| D | lsm_interface.rst | 14 use of a common code base for several different packet labeling protocols.
21 Since NetLabel supports multiple different packet labeling protocols and LSMs
22 it uses the concept of security attributes to refer to the packet's security
26 low-level packet label depending on the NetLabel build time and run time
43 Depending on the exact configuration, translation between the network packet
47 LSM has received a packet, used NetLabel to decode its security attributes,
50 identifier with the network packet's label. This means that in the future
51 when a incoming packet matches a cached value not only are the internal
|
| D | cipso_ipv4.rst | 19 Outbound Packet Processing
28 configured to use CIPSO for packet labeling then a CIPSO IP option will be
31 Inbound Packet Processing
36 to decode and translate the CIPSO label on the packet the LSM must use the
37 NetLabel security module API to extract the security attributes of the packet.
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy-p_sys-t | 8 tagged with this UUID in the MIPI SyS-T packet stream, to
19 length in each packet's metadata. This is normally redundant
28 MIPI SyS-T packet metadata, if this many milliseconds have
29 passed since the previous packet from this source. Zero is
36 Time interval in milliseconds. Send a CLOCKSYNC packet if
38 CLOCKSYNC packet from this source. Zero is the default and
|
| D | sysfs-class-net-queues | 7 Receive Packet Steering packet processing flow for this
16 Number of Receive Packet Steering flows being currently
41 Transmit Packet Steering packet processing flow for this
51 into the Transmit Packet Steering packet processing flow for this
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 35 would place each packet in contiguous physical memory. The driver also
59 In case of packet mechanism the single memory can be broken in smaller chunks
64 parameter image_type=packet. This can also be changed later as below::
66 echo packet > /sys/devices/platform/dell_rbu/image_type
68 In packet update mode the packet size has to be given before any packets can
73 In the packet update mechanism, the user needs to create a new file having
78 packet, the user needs to create more such packets out of the entire BIOS
107 Also echoing either mono, packet or init in to image_type will free up the
|
| /Documentation/networking/device_drivers/ethernet/amazon/ |
| D | ena.rst | 135 device fetches the ENA Tx descriptors and packet data from host
140 first 96 bytes of the packet directly to the ENA device memory
141 space. The rest of the packet payload is fetched by the
160 packet is running.
219 This option controls the maximum packet length for which the RX
220 descriptor it was received on would be recycled. When a packet smaller
284 ID is the index of the packet in the Tx info. This is used for
286 - Adds the packet to the proper place in the Tx ring.
295 - When the ENA device finishes sending the packet, a completion
300 completion descriptor per completed packet.
[all …]
|
12345678910>>...13