Lines Matching full:number

100 as well as TLS record sequence number. ``start_offload_tcp_sn`` indicates
101 which TCP sequence number corresponds to the beginning of the record with
102 sequence number from ``crypto_info``. The driver can add its state
112 number, simplifying TCP sequence number matching.
116 the expected sequence number and will have kernel record information.
124 so the initial records' TCP sequence number may be anywhere inside the segment.
134  * record metadata (sequence number, processing offset and length)
135  * expected TCP sequence number
138 segments may start at any point of a record and contain any number of records.
166 TLS handling and confirms the sequence number matches its expectation.
179 number is the expected one and proceeds to TLS handling (record delineation,
219 together with its TCP sequence number and TLS record number. The device
225 for a continuation with the crypto state and the new sequence number
237 sequence number is lower than expected the driver assumes retransmission
249 sequence number (as it will be updated from a different context).
256 Next time ``ktls`` pushes a record it will first send its TCP sequence number
257 and TLS record number to the driver. Stack will also make sure that
308 numbers more than a max size record past the expected TCP sequence number,
319 really starts there), and which record sequence number the given header had.
321 the record sequence number. Meanwhile, the device had been parsing
322 and counting all records since the just-confirmed one, it adds the number
323 of records it had seen to the record number provided by the kernel.
347 the next expected record number and its TCP sequence number. If the
410 The number of connections device can support can be exposed via
427  * ``rx_tls_decrypted_packets`` - number of successfully decrypted RX packets
429  * ``rx_tls_decrypted_bytes`` - number of TLS payload bytes in RX packets
431  * ``rx_tls_ctx`` - number of TLS RX HW offload contexts added to device for
433  * ``rx_tls_del`` - number of TLS RX HW offload contexts deleted from device
435  * ``rx_tls_resync_req_pkt`` - number of received TLS packets with a resync
437  * ``rx_tls_resync_req_start`` - number of times the TLS async resync request
439  * ``rx_tls_resync_req_end`` - number of times the TLS async resync request
441  * ``rx_tls_resync_req_skip`` - number of times the TLS async resync request
443  * ``rx_tls_resync_res_ok`` - number of times the TLS resync response call to
445  * ``rx_tls_resync_res_skip`` - number of times the TLS resync response call to
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
453  * ``tx_tls_ctx`` - number of TLS TX HW offload contexts added to device for
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