From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 23 17:36:02 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63CB416A46B; Wed, 23 Jan 2008 17:36:02 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 1625013C44B; Wed, 23 Jan 2008 17:36:01 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 541541B10EF4; Wed, 23 Jan 2008 18:36:00 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, J_CHICKENPOX_48 autolearn=no version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 55E1F1B10EE7; Wed, 23 Jan 2008 18:35:50 +0100 (CET) Message-ID: <47977AF5.7090906@moneybookers.com> Date: Wed, 23 Jan 2008 19:35:49 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.9 (X11/20071120) MIME-Version: 1.0 To: Steven Hartland References: <4795CC13.7080601@moneybookers.com><4795FE54.9090606@moneybookers.com> <86lk6i0vzk.fsf@ds4.des.no><479605E2.6070709@moneybookers.com> <47964356.6030602@moneybookers.com> <479647FB.3070909@FreeBSD.org><47970EE2.5000400@moneybookers.com> <479754E6.1060101@moneybookers.com> <9bbcef730801230802n5c52832bk60c6afc47be578f4@mail.gmail.com> <01ad01c85dda$9d2069e0$b6db87d4@multiplay.co.uk> In-Reply-To: <01ad01c85dda$9d2069e0$b6db87d4@multiplay.co.uk> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/5531/Wed Jan 23 11:32:09 2008 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: gettimeofday() in hping X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 17:36:02 -0000 Greetings, Steven Hartland wrote: > ----- Original Message ----- From: "Ivan Voras" >>> The other thing that bothers me is, that under freebsd is quite easy >>> to get: >>> [send_ip] sendto: No buffer space available >>> It happens almost always on my laptop just few seconds after I start >>> hping with timecounter=TSC >> >> I'm not sure, but from what I understood of Robert Watson's >> explanation in the big ZFS thread on -current, maybe increasing >> kmem_size (exactly as for ZFS...) could help you with these buffers. > > Is this not just running out of mbufs? netstat -m will show if it is > and the fix > is to just increase kern.ipc.nmbclusters. 670/1520/2190 mbufs in use (current/cache/total) 462/322/784/25600 mbuf clusters in use (current/cache/total/max) 462/306 mbuf+clusters out of packet secondary zone in use (current/cache) 0/35/35/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 1091K/1164K/2255K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/4/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines kern.ipc.nmbclusters: 25600 I do not think I'm running out of mbufs. And increasing nmbclusters doesn't help. Here is what I have for kmem_size. How can I see how much of the kmem size is used ? vmstat -m :) vm.kmem_size_scale: 3 vm.kmem_size_max: 335544320 vm.kmem_size_min: 0 vm.kmem_size: 335544320 Something suspicious that I notice is: vmstat -m|grep devbuf devbuf 5214 42780K - 6390 16,32,64,128,256,512,1024,2048,4096 42MB memory allocated for devbuf ? Is this ok ? This is the only thing that 'eat' more then 1-2MB memory reported by vmstat -m. -- Best Wishes, Stefan Lambrev ICQ# 24134177