From owner-freebsd-stable Wed May 19 12:41:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 5E4DA14D38 for ; Wed, 19 May 1999 12:41:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00519; Wed, 19 May 1999 12:38:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905191938.MAA00519@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Greg Quinlan" Cc: "Geff Hanoian" , freebsd-stable@FreeBSD.ORG Subject: Re: Memory leaks & kernel panic/reboot & ahc reboot In-reply-to: Your message of "Wed, 19 May 1999 18:57:28 BST." <012201bea221$0faeffa0$380051c2@greg.qmpgmc.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 12:38:51 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So Geff... > > Maybe you can educate me then.... > > After processes have taken all available memory (malloc) down to the > threshold... > What type of memory would be used next? Malloc doesn't allocate physical memory, it allocates virtual memory. Physical memory is allocated by the VM system to back virtual memory as required, and recycled when it's not. Malloc activity and physical memory usage are more or less completely unrelated; you can't draw any connections between them without a far deeper understanding of the system. In your case, I strongly suggest going back to basics and avoiding jumping to conclusions. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message