From owner-freebsd-hackers Sun Dec 30 23:29: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0BBAC37B423 for ; Sun, 30 Dec 2001 23:28:58 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBV7SuQ19094; Sun, 30 Dec 2001 23:28:56 -0800 (PST) (envelope-from dillon) Date: Sun, 30 Dec 2001 23:28:56 -0800 (PST) From: Matthew Dillon Message-Id: <200112310728.fBV7SuQ19094@apollo.backplane.com> To: "Anjali Kulkarni" Cc: , Subject: Re: Kernel Memory Limit References: <006e01c1905f$25fd1380$0a00a8c0@indranet> <20011229164322.A73212@freebsd.org.ru> <002801c191c2$9c497fb0$0a00a8c0@indranet> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi, : :I have tried this too, it makes absoutely no difference at all. My mallocs :fail after a certain no. of runs of my code(and there is no memory leak), :and there was no difference by increasing MAXDSIZ/DFLDSIZ. : :Thanks, :Anjali MAXDSIZ and DFLDSIZ are associated with USER malloc()s, not kernel malloc()s. If you are trying to use malloc() in kernel code there are some rather severe limits. 'vmstat -m' will give you a rundown on the statistics. KVM is only 1G, and a lot of is used-up. You cannot allocate (directly map) hundreds of megabytes of kernel memory. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message