mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-12 00:39:32 +00:00
haproxy public development tree
a9568411e4
We want to be able to resend frames from list of frames during handshakes to resend datagrams with the same frames as during the first transmissions. This leads to decrease drasctically the chances of frame fragmentation due to variable lengths of the packet fields. Furthermore the frames were not duplicated when retransmitted from a packet to another one. This must be the case only during packet loss dectection. qc_dup_pkt_frms() is there to duplicate the frames from an input list to an output list. A distinction is made between STREAM frames and the other ones because we can rely on the "acknowledged offset" the aim of which is to track the number of bytes which were acknowledged from TX STREAM frames. qc_release_frm() in addition to release the frame passed as parameter, also mark the duplicate STREAM frames as acknowledeged. qc_send_hdshk_pkts() is the qc_send_app_pkts() counterpart to send datagrams from at most two list of frames to be able to coalesced packets from two different packet number spaces qc_dgrams_retransmit() is there to probe the peer with datagrams depending on the need of the packet number spaces which must be flag with QUIC_FL_PKTNS_PROBE_NEEDED by the PTO timer task (qc_process_timer()). |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)