Lines Matching full:segment

110 After TX state is installed, the stack guarantees that the first segment
125 inside the segment.
142 to be possible, the device has to keep a small amount of segment-to-segment
145  * partial headers (if a segment carried only a part of the TLS header)
148    authentication tag has to be written or read from the subsequent segment)
188 corresponding to the segment. Networking stack makes sure decrypted
216 Whenever an out of order segment is transmitted the driver provides
219 segment has to be passed to the device as part of the packet context,
227 (next expected segment is the one after the out of order one), or continue
228 with the previous stream state - assuming that the out of order segment
236 Whenever an out of order segment is detected the driver requests
237 that the ``ktls`` software fallback code encrypt it. If the segment's
239 and doesn't change device state. If the segment is in the future, it
259 the new record will start on a segment boundary (like it does when
270    :alt:	reorder of non-header segment
273    Reorder of non-header segment
278 In above case segment 1 is received and decrypted successfully.
279 Segment 2 was dropped so 3 arrives out of order. The device knows
280 the next record starts inside 3, based on record length in segment 1.
281 Segment 3 is passed untouched, because due to lack of data from segment 2
282 the remainder of the previous record inside segment 3 cannot be handled.
284 and partial block from the new record in segment 3 and when 4 and 5
291 Kernel synchronization may be necessary if the lost segment contained
295    :alt:	reorder of header segment
298    Reorder of segment with a TLS header
300 In this example segment 2 gets dropped, and it contains a record header.
301 Device can only detect that segment 4 also contains a TLS header
302 if it knows the length of the previous record from segment 2. In this case
326 segment boundary.
380 For example authentication failure for any record in the segment should
417 Offload performance may depend on segment and record size.
517 Segment drops