a9de7ea1dc
Sending is done with several iterations over qcs streams in qc_send(). The first loop is conducted over streams in <qcc.send_list>. After this first iteration, some streams may still have data in their Tx buffer but were blocked by a full qc_stream_desc buffer. In this case, they have release their qc_stream_desc buffer in qcc_streams_sent_done(). New iterations can be done for these streams which can allocate new qc_stream_desc buffer if available. Before this patch, this was done through another stream list <qcc.send_retry_list>. Now, we can reuse the new <qcc.send_list> for this usage. This is safe to use as after first iteration, we have guarantee that either one of the following is true if there is still streams in <qcc.send_list> : * transport layer has rejected data due to congestion * stream is left because it is blocked on stream flow control * stream still has data and has released a fulfilled qc_stream_desc buffer. Immediate retry is useful for these streams : they will allocate a new qc_stream_desc buffer if possible to continue sending. This must be backported up to 2.7.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)