From owner-freebsd-stable Thu Oct 12 8:16: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id D812A37B503 for ; Thu, 12 Oct 2000 08:15:59 -0700 (PDT) Received: (qmail 27286 invoked from network); 12 Oct 2000 15:15:58 -0000 Received: from acs-24-154-28-99.zoominternet.net (HELO topperwein.dyndns.org) (24.154.28.99) by scully.zoominternet.net with SMTP; 12 Oct 2000 15:15:58 -0000 Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.0/8.11.0) with ESMTP id e9CFG7801405 for ; Thu, 12 Oct 2000 11:16:08 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Thu, 12 Oct 2000 11:16:07 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: FreeBSD-Stable Subject: RE: mbuf leakage on 4.1.1-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Oct 2000, Matt Heckaman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I thought I would through this into the mix: > > Server, NOT in production yet: 4.1.1-RELEASE: > > matt[beta]:~> uptime;netstat -m > 10:40AM up 16 days, 1:42, 2 users, load averages: 0.00, 0.00, 0.00 > 132/352/131072 mbufs in use (current/peak/max): > 130 mbufs allocated to data > 2 mbufs allocated to packet headers > 128/316/32768 mbuf clusters in use (current/peak/max) > 720 Kbytes allocated to network (40% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > Heavy Use Workstation, 4.1.1-RELEASE: > > 10:42AM up 16 days, 49 mins, 9 users, load averages: 0.28, 0.20, 0.17 > 693/1712/131072 mbufs in use (current/peak/max): > 132 mbufs allocated to data > 561 mbufs allocated to packet headers > 131/1410/32768 mbuf clusters in use (current/peak/max) > 3248 Kbytes allocated to network (13% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > So what you're showing below looks pretty normal. Note: I KNOW that I have > a small leak on epsilon. It's from wmbiff, which holds up descriptors like > you would believe. Gotta shut it down every couple of weeks to clear it > out, it's quite funny. Just to give a roug idea: > > root[epsilon]:~# lsof -p 98037 | wc -l > 3225 behanna@topperwein> netstat -m 211/272/8192 mbufs in use (current/peak/max): 181 mbufs allocated to data 30 mbufs allocated to packet headers 175/182/2048 mbuf clusters in use (current/peak/max) 432 Kbytes allocated to network (93% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines behanna@topperwein> uptime 11:11AM up 4:42, 6 users, load averages: 0.06, 0.02, 0.00 This is a box sitting on the end of a cable modem in my basement office. it doesn't see a large network load, although I'm blocking about 900 spam attempts per day (the same two bozos with forged addresses keep retrying every five minutes, and I keep 550-ing them. Now, it could be that my ISP is retrying to send these messages, which wouldn't surprise me :-( ). By tonight, I expect to see around 500 mbuf clusters in use, and a comparable number of mbufs in use. By late tomorrow, it will be time to reboot. :-( -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message