Re: [net-next PATCH 0/3] net: optimize ICMP-reply code path

2017-01-09 Thread David Miller
From: Jesper Dangaard Brouer Date: Mon, 09 Jan 2017 16:03:59 +0100 > This patchset is optimizing the ICMP-reply code path, for ICMP packets > that gets rate limited. A remote party can easily trigger this code > path by sending packets to port number with no listening service. > > Generally the

Re: [net-next PATCH 0/3] net: optimize ICMP-reply code path

2017-01-09 Thread Eric Dumazet
On Mon, 2017-01-09 at 09:43 -0800, Cong Wang wrote: > On Mon, Jan 9, 2017 at 7:03 AM, Jesper Dangaard Brouer > wrote: > > > > Use-case: The specific case I experienced this being a bottleneck is, > > sending UDP packets to a port with no listener, which obviously result > > in kernel replying with

Re: [net-next PATCH 0/3] net: optimize ICMP-reply code path

2017-01-09 Thread Cong Wang
On Mon, Jan 9, 2017 at 7:03 AM, Jesper Dangaard Brouer wrote: > > Use-case: The specific case I experienced this being a bottleneck is, > sending UDP packets to a port with no listener, which obviously result > in kernel replying with ICMP Destination Unreachable (type:3), Port > Unreachable (code

[net-next PATCH 0/3] net: optimize ICMP-reply code path

2017-01-09 Thread Jesper Dangaard Brouer
This patchset is optimizing the ICMP-reply code path, for ICMP packets that gets rate limited. A remote party can easily trigger this code path by sending packets to port number with no listening service. Generally the patchset moves the sysctl_icmp_msgs_per_sec ratelimit checking to earlier in th