-
Notifications
You must be signed in to change notification settings - Fork 127
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(udp): handle multiple datagrams on GRO (#1708)
* Test multi packet GRO read * fix(udp): handle multiple datagrams through gro Previously `Socket::recv` would at most return a single `Datagram` (i.e. `-> Result<Option<Datagram>, io::Error>`). When supported by the OS, the underlying `quinn-udp` can use both recvMmsg and GRO, each with the ability to return one or more datagrams. As of today, `neqo_common::udp` does not make use of recvmmsg, i.e. it only provides a single `IoSliceMut` to write into. That said, that single `IoSliceMut` might contain multiple `Datagram`s through GRO. Previously this would have been provided as a single `Datagram` to the caller of `Socket::recv`. This commit makes sure to handle the case where many `Datagram`s are retrieved via GRO (see `meta.stride` flag). It updates `neqo_common::udp::Socket::recv` and `neqo-server` and `neqo-client` accordingly. * fix: support single gso sendmmsg to result in multiple gro recvmmsg E.g. the case on CI on windows runner. * Reduce diff in client
- Loading branch information
Showing
3 changed files
with
86 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters