From owner-freebsd-isp  Sun Aug  8  9:34:13 1999
Delivered-To: freebsd-isp@freebsd.org
Received: from etinc.com (et-gw.etinc.com [207.252.1.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id D8B1C14BB8; Sun,  8 Aug 1999 09:34:08 -0700 (PDT)
	(envelope-from dennis@etinc.com)
Received: from workstation.etinc.com (port34.netsvr1.cst.vastnet.net [207.252.73.34])
	by etinc.com (8.9.3/8.9.3) with SMTP id MAA02351;
	Sun, 8 Aug 1999 12:26:04 -0400 (EDT)
Message-Id: <199908081626.MAA02351@etinc.com>
X-Sender: dennis@mail.etinc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Mon, 09 Aug 1999 00:41:13 -0400
To: hackers@freebsd.org
From: Dennis <dennis@etinc.com>
Subject: Routing Table Memory
Cc: isp@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


What flavor of memory tuning can be used to figure out how much the routing
table will have (and what tool can be used to monitor it, other than the
total usage shown in vmstat)?

A machine with 64M refuses to allocate more than ~10M (about 36K routes) no
matter how many users or clusters are allocated. NetBSD systems have no
trouble holding full tables (17M) in a 64k system.

Not that 128M is so expensive, but I'd like to know how to optimize it for
more efficient usage of memory.

Dennis



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message