Lines Matching full:packet

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
182 Device indicates successful handling of TLS offload in the per-packet context
185 Upon reception of a TLS offloaded packet, the driver sets
194 In presence of packet drops or network packet reordering, the device may lose
218 segment has to be passed to the device as part of the packet context,
222 the actual packet.
334 asynchronously to the packet stream and record may get processed
368 in the packet being dropped. For example if a packet got out of order
370 be encrypted such packet must be dropped.
376 side it should pass the packet to the host's networking stack as it was
380 result in passing the unmodified packet to the software fallback. This means
382 decryption is not advised. In other words either all records in the packet
383 had been handled successfully and authenticated or the packet has to be passed
384 to the host's stack as it was on the wire (recovering original packet in the
387 The Linux networking stack does not provide a way of reporting per-packet
391 A packet should also not be handled by the TLS offload if it contains
479 or virtual networking. However, many packet transformations performed
496 A device is permitted to perform packet reordering for consecutive
510 The device should not modify any packet headers for the purpose
513 The device should not depend on any packet headers beyond what is strictly