Lines Matching refs:packet
62 when a packet containing them is lost. This has the advantage of using
86 - The ability to determine, when the ACK Manager determines that a packet has
89 - What stream IDs were sent in a packet, and the logical ranges of application
95 - The logical ranges of the CRYPTO stream which were sent in the packet
98 - Which stream IDs had a FIN bit set in the packet.
103 - What control frames using the **GCR** strategy were sent in the packet
107 that frame type was contained in the packet (so that the flag can be set
108 again if the packet was lost).
133 to the `TX` state. If the packet it was sent in is subsequently lost,
140 When a packet containing a CFQ item is acknowledged, the CFQ is informed and the
163 * packet. They may be used for any purpose.
208 * priority determines the relative ordering of control frames in a packet.
210 * a packet. pn_space is a QUIC_PN_SPACE_* value.
288 in each packet, via a linked list of `QUIC_CFQ_ITEM`s.
291 for each frame type indicating whether the packet contained
294 - Keeping track of all stream IDs sent in a given packet, and
301 Manager's `QUIC_ACKM_TX_PKT` structure into its per-packet bookkeeping
303 allocation made per transmitted packet. The TX packetiser will obtain
324 /* Linked list of CFQ items in this packet. */
350 * Whether a FIN was sent for this stream in the packet. Not valid for
367 * Releases the TXPIM packet, returning it to the pool.
371 /* Clears the chunk list of the packet, removing all entries. */
374 /* Appends a chunk to the packet. The structure is copied. */
378 /* Adds a CFQ item to the packet by prepending it to the retx_head list. */
384 * given packet. The caller must call ossl_quic_txpim_pkt_get_num_chunks() to
412 The FIFD is used by obtaining a packet structure from the TXPIM, filling it in,
413 and then calling `ossl_quic_fifd_pkt_commit()`. The FIFD submits the packet to
414 the ACK Manager as a transmitted packet and provides its own callback
415 implementations to the ACK Manager for the packet. Note that the
417 once a packet's fate is known (acked, lost or discarded), use is immediately
423 subsystems in the event of a packet being acked, lost or discarded. In
469 and clears it when transmitting a packet containing such a frame.
479 is desired, and if so adds it to the packet.
482 in a packet. It does this before adding STREAM or CRYPTO frames (i.e.,
484 it places in a packet, it:
487 as having been transmitted in the given packet, so that the CFQ item can be
488 released or requeued depending on the ultimate fate of the packet.
490 - For each STREAM or CRYPTO frame included in a packet, the TX Packetiser:
500 fate of the packet.
503 of submitting the packet to the ACK Manager and provides its own callback
508 In the event of packet loss, ACK or discard, the appropriate QUIC Send Stream,
