Re: Kernel UDP behavior with missing destinations

2019-05-16 Thread Adam Urban
efinitely don't want it filling up buffers with useless/old packets!) On Thu, May 16, 2019 at 12:05 PM Eric Dumazet wrote: > > > > On 5/16/19 7:47 AM, Willem de Bruijn wrote: > > On Wed, May 15, 2019 at 3:57 PM Adam Urban wrote: > >> > >> We have an applicati

Re: Kernel UDP behavior with missing destinations

2019-05-16 Thread Adam Urban
e.com/spreadsheets/d/1t9_UowY6sok8xvK8Tx_La_jB4iqpewJT5X4WANj39gg/edit?usp=sharing On Thu, May 16, 2019 at 1:03 PM Eric Dumazet wrote: > > > > On 5/16/19 9:32 AM, Adam Urban wrote: > > Eric, thanks. Increasing wmem_default from 229376 to 2293760 indeed > > makes the issue go

Re: Kernel UDP behavior with missing destinations

2019-05-16 Thread Adam Urban
Eric, thanks. Increasing wmem_default from 229376 to 2293760 indeed makes the issue go away on my test bench. What's a good way to determine the optimal value here? I assume this is in bytes and needs to be large enough so that the SO_SNDBUF doesn't fill up before the kernel drops the packets. How

Re: Kernel UDP behavior with missing destinations

2019-05-16 Thread Adam Urban
0005,0005,,,,,,,,21af,,, 0005,,,,,,,,,,,, On Thu, May 16, 2019 at 10:48 AM Willem de Bruijn wrote: > > On Wed, May 15, 2019 at 3:57 PM Adam Urban

Kernel UDP behavior with missing destinations

2019-05-15 Thread Adam Urban
We have an application where we are use sendmsg() to send (lots of) UDP packets to multiple destinations over a single socket, repeatedly, and at a pretty constant rate using IPv4. In some cases, some of these destinations are no longer present on the network, but we continue sending data to them