Lines Matching refs:which
4 The QUIC frame-in-flight manager is responsible for tracking frames which were
5 sent which need to be regenerated if the packets they were placed into are
82 - Need for a generic control queue which can store encoded control frames.
84 most control frames which do not have special requirements.
90 data bytes for each (which may not be one contiguous range).
95 - The logical ranges of the CRYPTO stream which were sent in the packet
96 (which may not be one contiguous range), for similar reasons.
115 The CFQ (`QUIC_CFQ`) stores encoded frames which can be blindly retransmitted in
121 Each frame in the CFQ is a simple opaque byte buffer, which has the following
126 - The frame type, which is provided by the caller along with the buffer.
131 - A state, which is either `NEW` or `TX`. Frames added to the CFQ have
162 * TXPIM in keeping a list of GCR control frames which were sent in a
212 * On success, returns a QUIC_CFQ_ITEM pointer which acts as a handle to
279 allocating and keeping bookkeeping structures for packets which have been
287 - Keeping track of all GCR control frames which were transmitted
305 the ACK Manager data, and submit it via the FIFD which we introduce below.
427 - It references an ACK manager which it informs of transmitted packets;
428 - It references a TXPIM which manages each `QUIC_TXPIM_PKT`;
432 - It is provided with a callback which is called when it thinks a frame
434 to a given stream, in which case a stream ID is specified.
475 (`QUIC_ACKM_TX_PKT`), except for the callback fields, which are handled by the
505 which were added via `ossl_quic_txpim_pkt_add_cfq_item()` have been
