af22792a43
QUIC datagrams are encoded during emission via the function qc_prep_pkts(). By default, if GSO is not used, each datagram is prefixed by a metadata header which specify its length and address of its first quic_tx_packet instance. If GSO is activated, metadata header won't be inserted for datagrams following the first one sent in a single syscall. Length field will contain the total size of these datagrams. This allows to support both GSO and non-GSO prepared datagram in the same Tx buffer. qc_send_ppkts() is invoked just after datagrams encoding. It iterates over each metadata header in Tx buffer to sent each datagram individually. If length field is bigger than network MTU, GSO usage is assumed and qc_snd_buf() GSO parameter will be set. Another important point to note regarding GSO implementation is that during datagram encoding, packets from the same datagram instance are attached together. However, if using GSO, consecutive packets from different datagrams are also linked, but without QUIC_FL_TX_PACKET_COALESCED flag. This allows to properly update quic_conn status with all sent packets in qc_send_ppkts(). Packets from different datagrams are then unlinked to treat them separately when receiving corresponding ACK frames. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.