From owner-freebsd-i386@FreeBSD.ORG Wed Aug 19 21:37:38 2009 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C777B106568F; Wed, 19 Aug 2009 21:37:38 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BAC5B8FC45; Wed, 19 Aug 2009 21:37:38 +0000 (UTC) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7JLbc1R081137; Wed, 19 Aug 2009 21:37:38 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7JLbcSb081133; Wed, 19 Aug 2009 21:37:38 GMT (envelope-from remko) Date: Wed, 19 Aug 2009 21:37:38 GMT Message-Id: <200908192137.n7JLbcSb081133@freefall.freebsd.org> To: piroman@myconfig.ru, remko@FreeBSD.org, freebsd-i386@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: i386/137975: Not clearing of memory after file deletion from a ram-disk X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2009 21:37:38 -0000 Synopsis: Not clearing of memory after file deletion from a ram-disk State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Wed Aug 19 21:37:38 UTC 2009 State-Changed-Why: I think this is not a problem but misunderstanding about how FreeBSD's memory allocation works. As you see memory is being taken and 'released' after use, though not entirely; why? FreeBSD also uses the memory as caching mechanism. For example if you issue an ``ls`` and then do the ``ls`` again, you will see that the second time it will return much quicker; this is temporarily cached in memory to help you do repeated tasks quicker. If needed the memory is freed and used for 'more important' operations. On my systems I normally have 'limited' free memory available; I do not worry about this because I understand that it's the caching that 'takes' the memory and releases it when needed. Please ask around on the questions mailinglist if this was insufficient explanation. http://www.freebsd.org/cgi/query-pr.cgi?pr=137975