Date: Mon, 11 Apr 2011 14:21:30 +0700 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Przemyslaw Frasunek <przemyslaw@frasunek.com> Cc: freebsd-net@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org> Subject: Re: mpd5/Netgraph issues after upgrading to 7.4 Message-ID: <4DA2ABFA.7030108@rdtc.ru> In-Reply-To: <4DA2A5AA.4060802@frasunek.com> References: <4D947756.6050808@freebsd.lublin.pl> <4D9F6C71.1040209@frasunek.com> <4DA171BA.9000507@frasunek.com> <4DA1E39C.9090300@rdtc.ru> <4DA23090.8060206@frasunek.com> <20110411054932.GU84445@FreeBSD.org> <4DA2A5AA.4060802@frasunek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11.04.2011 13:54, Przemyslaw Frasunek wrote: >> IMO, any kind of memory allocation code (malloc, uma, netgraph item >> allocator) never return EPERM, they return ENOMEM or ENOBUFS. >> >> So, there is a bug somewhere else. > > I think so, but for me it still looks like resource shortage. As I wrote > before, when EPERM starts appearing, I'm unable to run "ngctl list". Increase sysctl kern.ipc.maxsockbuf. I was forced to rise it upto 80MB (sic!) as 8MB was not enough to me. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DA2ABFA.7030108>