From owner-freebsd-questions@FreeBSD.ORG Fri Sep 12 10:12:19 2003 Return-Path: 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 8A7D916A4BF for ; Fri, 12 Sep 2003 10:12:19 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B03EB43F75 for ; Fri, 12 Sep 2003 10:12:18 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h8CHCIfN055928; Fri, 12 Sep 2003 12:12:18 -0500 (CDT) (envelope-from dan) Date: Fri, 12 Sep 2003 12:12:18 -0500 From: Dan Nelson To: Jesse Guardiani Message-ID: <20030912171217.GD61528@dan.emsphone.com> References: <20030911231742.GA61528@dan.emsphone.com> <20030912163954.GC61528@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: freebsd-questions@freebsd.org Subject: Re: `top` process memory usage: SIZE vs RES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 17:12:19 -0000 In the last episode (Sep 12), Jesse Guardiani said: > Dan Nelson wrote: > > In the last episode (Sep 12), Jesse Guardiani said: > >> Dan Nelson wrote: > >> > In the last episode (Sep 11), Jesse Guardiani said: > >> > > >> >> 2.) What, exactly, is RES? `man top` describes it as this: > >> >> "RES is the current amount of resident memory", but does > >> >> that mean RES is included in SIZE? Or does that mean that > >> >> RES should be counted in addition to SIZE? > >> > > >> > RES the amount of SIZE that it currently in core > >> > >> OK. To clarify, you mean core kernel memory here? > >> If so, how is that significant? Why should I care? > >> > >> In other words, why would I ever want to know that? > > > > core meaning physical memory; user memory in this case. > > OK. And how does core, or user memory differ from SIZE memory > then? If X = SIZE - RES, where is X stored? You don't need to store it, since you know SIZE and RES :) X is any memory mapped into process space that is not in physical memory at the moment; it could be dirty or private pages swapped to disk, or program code that can be pulled from the binary on the filesystem if necessary, or malloced memory that hasn't been written to yet. -- Dan Nelson dnelson@allantgroup.com