Lines Matching full:demuxer

23  * QUIC Demuxer
26  * The QUIC connection demuxer is the entity responsible for receiving datagrams
36  * consulting a LCIDM instance. Thus the demuxer has no specific knowledge of
44  * Since the demuxer must handle the initial reception of datagrams from the OS,
46  * demuxer.
48  * The demuxer maintains a queue of Unprocessed RX Entries (URXEs), which store
54  * packets, however, this is not the demuxer's concern. QUIC prohibits different
55  * packets in the same datagram from containing different DCIDs; the demuxer
59  * examined by the demuxer, and the demuxer does not perform validation of
65  * are exposed. Since the demuxer is only exposed to other parts of the QUIC
74  *     when it is not being managed by the demuxer.
105      * has already been removed. Used by QRX only; not used by the demuxer.
130      * QRX only; not used by the demuxer.
159  * List management helpers. These are used by the demuxer but can also be used
160  * by users of the demuxer to manage URXEs.
170  * to mutate this buffer; once the demuxer calls this callback, it will never
187  * Creates a new demuxer. The given BIO is used to receive datagrams from the
204  * Destroy a demuxer. All URXEs must have been released back to the demuxer
210  * Changes the BIO which the demuxer reads from. This also sets the MTU if the
235  * Releases a URXE back to the demuxer. No reference must be made to the URXE or
283  * Artificially inject a packet into the demuxer for testing purposes. The
284  * buffer must not exceed the URXE size being used by the demuxer.