On Mon, Apr 11, 2011 at 12:34:56AM +0200, Przemyslaw Frasunek wrote: P> > Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column. P> > If you see non-zero values there, you need to increase netgraph memory limits P> > net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf. P> P> Unfortunately, increasing net.graph.maxdata & net.graph.maxalloc didn't P> solved EPERM problems on netgraph control sockets. It is still appearing P> every few hours, but failure counters are zero:
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. -- Totus tuus, Glebius. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
