Lines Matching refs:out

36 offload opt-in or opt-out on per-connection basis is not currently supported.
207 Segments transmitted from an offloaded socket can get out of sync
210 two mechanisms for dealing with out of order segments.
215 Whenever an out of order segment is transmitted the driver provides
226 (next expected segment is the one after the out of order one), or continue
227 with the previous stream state - assuming that the out of order segment
235 Whenever an out of order segment is detected the driver requests
278 Segment 2 was dropped so 3 arrives out of order. The device knows
287 spanning segments 1, 2 and 3. The device did not get out of sync,
307 When the device gets out of sync and the stream reaches TCP sequence
368 in the packet being dropped. For example if a packet got out of order
458    a TLS stream and arrived out-of-order, but skipped the HW offload routine
462    a TLS stream dropped, because they arrived out of order and associated
490 transmitted or received out of order, for example pure ACK packets