Add an opt-in UDP GRO mode to QuicPacketReader. With GRO, the kernel can hand a socket back-to-back datagrams of the same size from the same peer as one GRO train, which a single read returns. Supporting UDP GRO on the QUIC socket requires to configure the reader and the socket at QUIC client creation time. For the reader case, `QuicPacketReader` cannot read GRO trains today because its packet buffers can only hold one datagram, and it would treat a train as one packet. This change adds `QuicPacketReader::Options::enable_gro`. When it is set, the reader uses packet buffers large enough for a whole train (64 KB per slot instead of 1,472 bytes, about 1 MB per reader), asks for the GRO segment size on each read, and dispatches each packet of a train separately, with the train's addresses, receipt time, and other per-datagram metadata. For the socket case, this adds `QuicUdpSocketApi::EnableUdpGro` to set the UDP_GRO socket option. Readers will only allocate the GRO-sized buffers when explicitly passing the option at creation time, so behavior is unchanged for existing users. PiperOrigin-RevId: 1019227871
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.
QUICHE has binaries that can run on Linux platforms.
Follow the instructions to install Bazel.
sudo apt install libicu-dev clang lld cd <directory that will be the root of your quiche implmentation> git clone https://github.com/google/quiche.git cd quiche CC=clang bazel build -c opt //... ./bazel-bin/quiche/<target_name> <arguments>
There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
Usage: quic_client <URL>
quic_server: listens forever on --port (default 6121) until halted via ctrl-c.
masque_client: tunnels to a URL via an identified proxy (See RFC 9298).
Usage: masque_client [options] <proxy-url> <urls>
Usage: masque_server
web_transport_test_server: a server that clients can connect to via WebTransport.
moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.
Usage: moqt_relay
Most log messages in QUICHE use the QUICHE_DLOG macro. In standalone quiche, these all either go to stderr, or are suppressed, based on the --stderrthreshold flag.
To send INFO level log messages to a file, you would therefore invoke
<binary> <args> > <logfile> 2>&1
Use the --helpfull flag for more.