Commit f1063cb
committed
Increase GRO segments to 64
Unless the sender and the receiver agree on the exact size of the
datagrams they're going to exchange, there's no way to know the GRO
segment size before calling recvmmsg(). This makes it impossible to
calculate how big the receive buffer should be before calling
recvmmsg(), potentially leading to truncated segments if it isn't a
multiple of the GRO segment size.
Bumping gro::gro_segments() to the max allowed by the kernel
(UDP_GRO_CNT_MAX = 64), and assuming that get_max_udp_payload_size() is
a valid upper bound for incoming datagrams, ensures that the receive
window we allocate is always large enough.1 parent 29d3932 commit f1063cb
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
645 | 645 | | |
646 | 646 | | |
647 | 647 | | |
648 | | - | |
| 648 | + | |
| 649 | + | |
| 650 | + | |
649 | 651 | | |
650 | 652 | | |
651 | 653 | | |
| |||
0 commit comments