From owner-freebsd-hardware@FreeBSD.ORG Fri Aug 11 08:11:15 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8012816A4DA; Fri, 11 Aug 2006 08:11:15 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB14843D46; Fri, 11 Aug 2006 08:11:14 +0000 (GMT) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 0AC1B37AD9; Fri, 11 Aug 2006 11:11:12 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21321-05; Fri, 11 Aug 2006 11:11:11 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 0F0C637AC5; Fri, 11 Aug 2006 11:11:11 +0300 (EEST) Message-ID: <44DC3B92.3010804@bulinfo.net> Date: Fri, 11 Aug 2006 11:10:58 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: John Baldwin References: <200608090908.k79988pY086073@fire.jhs.private> <200608091431.50183.jhb@freebsd.org> <44DA46D3.3040504@lbl.gov> <200608091712.48401.jhb@freebsd.org> In-Reply-To: <200608091712.48401.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: Julian Stacey , "Jin Guojun \[VFFS\]" , freebsd-hardware@freebsd.org Subject: Re: Real and available memory? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2006 08:11:15 -0000 John Baldwin wrote: > On Wednesday 09 August 2006 16:34, Jin Guojun [VFFS] wrote: > > Please don't use HTML-only e-mail. > > >>> Well, that's where the missing 40 meg is. :) The kernel text (including >>> any modules and preloaded mfsroot's) aren't include in the 'avail memory' >>> count. >>> >> This is not where the memory goes. >> The MFS root is probably not allocated yet at this point. >> > > Huh? Of course it is! You load it from /boot/loader into RAM at the same > point when you load the kernel. All of the kernel text plus any loaded > modules are not considered available memory when 'avail memory' is output. > (Along with a few other pages needed for things like crashdumps, some VM > bootstrapping data structures, etc.) You can't load a MFS root after the > kernel is booted because if it's the root filesystem, there's no place for > it to be loaded from once the kernel boots. > > Absolutely correct! I have decreased the size of mfsroot image with 4Mb and available memory is 4Mb up. Thanks for all replays