From owner-freebsd-net@FreeBSD.ORG  Wed Sep 10 16:06:30 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E04C616A4BF
	for <net@freebsd.org>; Wed, 10 Sep 2003 16:06:30 -0700 (PDT)
Received: from venus.vincentjardin.net
	(AVelizy-102-1-2-67.w217-128.abo.wanadoo.fr [217.128.206.67])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5604D43FE3
	for <net@freebsd.org>; Wed, 10 Sep 2003 16:06:29 -0700 (PDT)
	(envelope-from jardin@venus.vincentjardin.net)
Received: from venus.vincentjardin.net (localhost [127.0.0.1])
	h8AN6UnK004807
	for <net@freebsd.org>; Thu, 11 Sep 2003 01:06:30 +0200 (CEST)
	(envelope-from jardin@venus.vincentjardin.net)
Received: by venus.vincentjardin.net (8.12.9/8.12.9/Submit) id h8AN6TGt004806
	for net@freebsd.org; Thu, 11 Sep 2003 01:06:29 +0200 (CEST)
From: Vincent Jardin <vjardin@free.fr>
To: net@freebsd.org
Date: Thu, 11 Sep 2003 01:06:28 +0200
User-Agent: KMail/1.5.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200309110106.28960.vjardin@free.fr>
Subject: KMAP ENTRY limit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2003 23:06:31 -0000

Hi,

I get a FreeBSD 4.8 that reaches the limit of KMAP ENTRY whereas it remains 
enough free memory. How is computed this limit and how can it be increased ?

$ vmstat -z
ITEM            SIZE     LIMIT    USED    FREE  REQUESTS
  ...
KMAP ENTRY:       48,     7933,    130,    168,     1037
(panic when SIZE >= LIMIT)

Moreover, why should vm_map_entry_create() panic when zalloc() returns NULL ? 
I think one can return NULL without panicing. Is it a bug or a feature ?

Regards,
  Vincent