From owner-freebsd-questions@FreeBSD.ORG  Wed Jul  9 15:28:39 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 76A2237B404
	for <freebsd-questions@freebsd.org>;
	Wed,  9 Jul 2003 15:28:39 -0700 (PDT)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id BC65D43FBD
	for <freebsd-questions@freebsd.org>;
	Wed,  9 Jul 2003 15:28:37 -0700 (PDT)	(envelope-from silby@silby.com)
Received: (qmail 83131 invoked from network); 9 Jul 2003 22:28:36 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 9 Jul 2003 22:28:36 -0000
X-pair-Authenticated: 209.68.2.70
Date: Wed, 9 Jul 2003 17:28:08 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Thomas Chaffic Mowad <tm@owlnet.rice.edu>
In-Reply-To: <Pine.GSO.4.33.0307091558090.29385-100000@short-eared.owlnet.rice.edu>
Message-ID: <20030709172625.M11890@odysseus.silby.com>
References: <Pine.GSO.4.33.0307091558090.29385-100000@short-eared.owlnet.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-hackers@freebsd.org
cc: freebsd-questions@freebsd.org
cc: tm@rice.edu
Subject: Re: kern.ipc.maxsockets limits with 4GB of memory
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2003 22:28:39 -0000


On Wed, 9 Jul 2003, Thomas Chaffic Mowad wrote:

> Someone thought that the kernel might need more memory so we tried
> increasing VM_KMEM_MAXSIZE too 500 megs and then that caused a panic when
> we booted up.
>
> So we're kinda stuck here and any help would be greatly appreciated.
>
> Thanks,
> --Tom Mowad

Have you tried increasing KVA_PAGES?

#
# Change the size of the kernel virtual address space.  Due to
# constraints in loader(8) on i386, this must be a multiple of 4.
# 256 = 1 GB of kernel address space.  Increasing this also causes
# a reduction of the address space in user processes.  512 splits
# the 4GB cpu address space in half (2GB user, 2GB kernel).
#
options         KVA_PAGES=260

If that doesn't help, you may also consider trying 4.8-RELEASE or -STABLE;
I believe that some additional changes to fix handling of 4GB machines
were committed after 4.7-RELEASE.  (You'll have to search the mailinglist
archives to confirm this, I can't remember exactly when they occured.)

Also, how are you exhausting 128K sockets to do a test of 2000
simultaneous connections?  Are the rest all in the TIME_WAIT state?

Mike "Silby" Silbersack