From owner-freebsd-questions@FreeBSD.ORG Fri Sep 12 10:06:50 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 E423516A4BF for ; Fri, 12 Sep 2003 10:06:50 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34D9843F93 for ; Fri, 12 Sep 2003 10:06:48 -0700 (PDT) (envelope-from freebsd-questions@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19xrNY-00034T-00 for ; Fri, 12 Sep 2003 19:06:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19xrNX-00034L-00 for ; Fri, 12 Sep 2003 19:06:39 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 19xrNd-0007ji-00 for ; Fri, 12 Sep 2003 19:06:45 +0200 From: Jesse Guardiani Date: Fri, 12 Sep 2003 13:06:44 -0400 Organization: WingNET Lines: 42 Message-ID: References: <20030911231742.GA61528@dan.emsphone.com> <20030912163954.GC61528@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: `top` process memory usage: SIZE vs RES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 17:06:51 -0000 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? > Processes can > lock kernel memory, but there's no easy way of listing that (it's > usually a small amount held in pipe or socket buffers and is > short-lived). The name "core" came from when memory bits were ferrite > rings magnetized by wires running through them. > > http://www.columbia.edu/acis/history/core.html Wow. That's a really cool bit of history. I don't quite understand how a core is "switched", but I'm sure it must have worked. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net