From owner-freebsd-performance@FreeBSD.ORG Fri May 27 01:44:29 2005 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5241E16A41C for ; Fri, 27 May 2005 01:44:29 +0000 (GMT) (envelope-from pfak@telus.net) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id E77FA43D1D for ; Fri, 27 May 2005 01:44:28 +0000 (GMT) (envelope-from pfak@telus.net) Received: from [192.168.1.151] (really [64.180.103.26]) by priv-edtnes46.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050527014427.QDTV22705.priv-edtnes46.telusplanet.net@[192.168.1.151]> for ; Thu, 26 May 2005 19:44:27 -0600 Message-ID: <42967B7E.1020607@telus.net> Date: Thu, 26 May 2005 18:44:30 -0700 From: Peter Kieser User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-performance@freebsd.org References: <1117129668.42960bc4b751b@webmail.telus.net> In-Reply-To: <1117129668.42960bc4b751b@webmail.telus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Performance/lockup issues with FreeBSD as a router (followup) X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2005 01:44:29 -0000 Hello, I fixed the problem. It appears that the kernel was running out of memory to allocate the network sockets, I took your guys suggestions (along with the kernel configurations and such), and the problem is now resolved. I also replaced the physical machine, but am using the same NICs for even better performance. If anyone is interested in the exact configuration I've used, I'll be happy to post. --Peter Peter Kieser wrote: >Hello guys, > >I'm not quite sure if this is the right list to address this to, as it's partly >a performance problem and partly otherwise. > >I have a FreeBSD machine acting as a router (doing approx. 15-25Mbit/s of >traffic (lot's of small packets, about 45,000 pps)), however I'm currently >running into issues where one, or both of the NICs will stop transmitting >traffic. When I go onto the machine, and try to ping something I get "No buffer >space available" > >The nics are if_dc, this is a stock FreeBSD 5.4-RELEASE installation (no >firewall or anything): > >Here's my /etc/sysctl.conf: > >net.inet.ip.rtexpire=1800 >net.inet.ip.rtminexpire=1800 >kern.maxfiles=32768 >kern.maxfilesperproc=32768 >kern.ipc.somaxconn=32767 >net.inet.tcp.sendspace=256000 >net.inet.tcp.recvspace=256000 >kern.ipc.maxsockbuf=2097152 >net.inet.ip.fastforwarding=1 >net.inet.tcp.rfc1323=1 >net.link.ether.inet.max_age=600 >net.inet.tcp.msl=7500 >net.inet.ip.fw.dyn_udp_lifetime=10 >net.inet.ip.fw.dyn_buckets=1024 > >And here's my /boot/loader.conf: > >kern.ipc.maxsockets="163840" >kern.maxusers="2048" > >Is there anythign I'm overlooking that would be causing the machine to lockup >like this? > >--Peter > >_______________________________________________ >freebsd-performance@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-performance >To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org" > > >