Date: Fri, 12 Sep 2003 12:12:18 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Jesse Guardiani <jesse@wingnet.net> Cc: freebsd-questions@freebsd.org Subject: Re: `top` process memory usage: SIZE vs RES Message-ID: <20030912171217.GD61528@dan.emsphone.com> In-Reply-To: <bjsuf5$t1b$1@sea.gmane.org> References: <bjqs64$6i9$1@sea.gmane.org> <20030911231742.GA61528@dan.emsphone.com> <bjsjdd$vgh$2@sea.gmane.org> <20030912163954.GC61528@dan.emsphone.com> <bjsuf5$t1b$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030912171217.GD61528>