From owner-freebsd-net Mon Feb 18 20:13: 6 2002 Delivered-To: freebsd-net@freebsd.org Received: from patrocles.silby.com (d154.as20.nwbl0.wi.voyager.net [169.207.139.156]) by hub.freebsd.org (Postfix) with ESMTP id 3195837B483 for ; Mon, 18 Feb 2002 20:10:27 -0800 (PST) Received: from patrocles.silby.com (localhost [127.0.0.1]) by patrocles.silby.com (8.12.2/8.12.2) with ESMTP id g1IME4FY000653; Mon, 18 Feb 2002 22:14:04 GMT (envelope-from silby@silby.com) Received: from localhost (silby@localhost) by patrocles.silby.com (8.12.2/8.12.2/Submit) with ESMTP id g1IMDxjL000650; Mon, 18 Feb 2002 22:14:01 GMT X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Mon, 18 Feb 2002 22:13:59 +0000 (GMT) From: Mike Silbersack To: Randy Bush Cc: Luigi Rizzo , Subject: Re: network buffer problem In-Reply-To: Message-ID: <20020218221129.J636-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 18 Feb 2002, Randy Bush wrote: > > If you have 4.5 and enough memory one option is to use > > MAXUSERS=0 and remove and "options NMBCLUSTERS" > > that's how it is now. > > before the latest builds, it uses to be MAXUSERS=96. maybe i should > revert that. > > and i have to open the box sometime soon, so i'll shove a bunch of > ram in it. > > randy Yep, the autoscaling would have chosen MAXUSERS=64, so you've been running with fewer NMBCLUSTERS than usual. OTOH, whatever extraordinary event that caused you to run out of mbuf clusters that one time may very well also run you out of mbuf clusters even at MAXUSERS=96; mbuf clusters tend to get eaten pretty quickly. Either way, adding ram sounds like a good idea. :) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message