Lines Matching full:flow

1 Flow Control
4 Introduction to QUIC Flow Control
7 QUIC flow control acts at both connection and stream levels. At any time,
8 transmission of stream data could be prevented by connection-level flow control,
9 by stream-level flow control, or both. Flow control uses a credit-based model in
10 which the relevant flow control limit is expressed as the maximum number of
14 It is important to note that both connection and stream-level flow control
15 relate only to the transmission of QUIC stream data. QUIC flow control at stream
18 again, this still only counts as one byte for the purposes of flow control. Note
25 believe we have exhausted our flow control credit whereas the peer believes we
27 advancing us more flow control credit.)
29 QUIC flow control at connection level is based on the sum of all the logical
32 Connection-level flow control is controlled by the `MAX_DATA` frame;
33 stream-level flow control is controlled by the `MAX_STREAM_DATA` frame.
40 purposes: to enhance flow control performance, and as a debugging aid.
44 to flow control.
46 Note that flow control and congestion control are completely separate
61 - **Controlled bytes** refers to any byte which counts for purposes of flow
69   Retirement is an important factor in our RX flow control design, as we want
78   amount of flow control budget which has been spent. It is a monotonic value
104   a flow control protocol violation has occurred and the connection
107 Connection-Level Flow Control - TX Side
110 TX side flow control is exceptionally simple. It can be modelled as the
148 We must not exceed the flow control limits, else the peer may terminate the
155 Stream-Level Flow Control - TX Side
158 Stream-level flow control works exactly the same as connection-level flow
170 both connection and stream-level flow control; thus the number of controlled
175 Connection-Level Flow Control - RX Side
181         <--- event: Flow Control Error
183 RX side connection-level flow control provides an indication of when to generate
187 The state machine receives On RX Controlled Bytes events from stream-level flow
189 a stream-level flow controller whenever we receive any controlled bytes.
191 generated by stream-level flow control as retransmitted stream data must be
192 counted only once, and the stream-level flow control is therefore in the best
197 the Flow Control Error event. The connection should be terminated with a
201 should be advanced more flow control credit (i.e., when the CWM should be
210 receives to determine when to increase the flow control window. Thus, the On
215 Stream-Level Flow Control - RX Side
218 RX-side stream-level flow control works similarly to RX-side connection-level
219 flow control. There are a few differences:
224   to a connection-level flow controller (an implementation decision), as these
237   the connection-level flow controller. It is also used by stream-level flow
238   control to determine if flow control limits are violated by the peer.
251 For RX flow control we must determine our window size. This is the value we add
269 For more information on auto-tuning, see [Flow control in
271 and [QUIC Flow