Lines Matching full:packets

25    on a packet by packet basis, provided the packets arrive in order.
47 Instead packets reach a device driver, the driver will mark the packets
56 :c:type:`struct sk_buff <sk_buff>`. The packets reach the TCP stack and
97 the received or transmitted packets. Driver uses the ``sk`` parameter
149 Record reassembly is not necessary for TLS offload. If the packets arrive
162 For segments passed in order, the driver marks the packets with
164 packets requiring HW offload, see the :ref:`5tuple_problems` section)
359 Packets may be redirected or rerouted by the stack to a different
381 packets should not be modified "in place". Splitting segments to handle partial
388 decryption and authentication errors, packets with errors must simply not
427  * ``rx_tls_decrypted_packets`` - number of successfully decrypted RX packets
429  * ``rx_tls_decrypted_bytes`` - number of TLS payload bytes in RX packets
435  * ``rx_tls_resync_req_pkt`` - number of received TLS packets with a resync
447  * ``rx_tls_err`` - number of RX packets which were part of a TLS stream
449  * ``tx_tls_encrypted_packets`` - number of TX packets passed to the device
451  * ``tx_tls_encrypted_bytes`` - number of TLS payload bytes in TX packets
455  * ``tx_tls_ooo`` - number of TX packets which were part of a TLS stream
457  * ``tx_tls_skip_no_sync_data`` - number of TX packets which were part of
461  * ``tx_tls_drop_no_sync_data`` - number of TX packets which were part of
464  * ``tx_tls_drop_bypass_req`` - number of TX packets which were part of a TLS
476 The device can only recognize received packets based on the 5-tuple
489 Introducing extra processing in NICs should not cause packets to be
490 transmitted or received out of order, for example pure ACK packets
497 TCP segments (i.e. placing packets in the correct order) but any form
505 in packets as seen on the wire.
519 Dropping packets is acceptable only in the event of catastrophic