Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Running out of buffers?

On 27/04/2018 21:34, Roy Marples wrote:
Hi Paul

On 27/04/2018 04:09, Paul Goyette wrote:
I've got lots of memory, so I don't understand what buffers are not
available.  Ever since upgrading to my current system (sources dated
2018-03-20 11:25:00 UTC), I've been seeing these messages at random

Can you test the below patches please?
The kernel part bumps the default raw socket buffer from 8k to 16k
At least my ERLITE no longer complains about route socket overflow on boot.

The patch to syslogd ensures that the logpath socket receive buffer is a minimum of 16k - the current default is 4k.

Hopefully this fixes the issues and won't impact small memory devices too much.

Another patch.
This time to handle a reported overflow listening to ND6.

Index: sys/netinet6/in6_proto.c
RCS file: /cvsroot/src/sys/netinet6/in6_proto.c,v
retrieving revision 1.122
diff -u -p -r1.122 in6_proto.c
--- sys/netinet6/in6_proto.c    15 Mar 2018 08:15:21 -0000      1.122
+++ sys/netinet6/in6_proto.c    1 May 2018 19:18:22 -0000
@@ -597,7 +597,7 @@ int pmtu_expire = 60*10;
  * Nominal space allocated to a raw ip socket.
 #define        RIPV6SNDQ       8192
-#define        RIPV6RCVQ       8192
+#define        RIPV6RCV2       16384

 u_long rip6_sendspace = RIPV6SNDQ;
 u_long rip6_recvspace = RIPV6RCVQ;

Home | Main Index | Thread Index | Old Index