Hi,
On Thu, Mar 08, 2018 at 04:02:22PM +0100, Arne Schwabe wrote:
> The discussion has gone on a bit about this patch. I would like to step
> back and give an overview to make this mess better understandable as we
> have multiple problem mixed together.
Since this summary is from March, and we've
Hi,
I'd thoroughly test this with protocols like Google's QUIC, which uses UDP
> underneath. How does it respond to such ICMP messages? what does it do to
> throughput?
>
I tested sending ICMP "destination unreachable/fragmentation needed" with
Chrome as QUIC client and
turns out that it fallback
Your patch has been applied to the master and release/2.4 branch.
Commit messages amended according to the comittee proposal ;-)
Uncrustify will complain to us that the switch/case block in push.c
grew an extra nesting level but indentation didn't change... but that's
just whitespace, so fixed on
