From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 29 05:28:27 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F004B106564A for ; Mon, 29 Dec 2008 05:28:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id CC38C8FC12 for ; Mon, 29 Dec 2008 05:28:27 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from eagle.syrec.org (c-24-6-210-197.hsd1.ca.comcast.net [24.6.210.197]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id mBT5DQue018221 for ; Sun, 28 Dec 2008 21:13:26 -0800 (PST) Message-ID: <49585C75.80203@rawbw.com> Date: Sun, 28 Dec 2008 21:13:25 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.18 (X11/20081127) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How process size is calculated? Is it always based on the current highest available address in memory space? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2008 05:28:28 -0000 malloc(3) can be controlled by MALLOC_OPTIONS to use mmap-based allocation as opposed to sbrk-based allocation. But allocations/deallocations with mmaps can eventually lead to non-continuously mmapped memory (having some non-mmapped gaps). Are these gaps excluded from the process size or size is always linked to the current highest available address in memory space? Yuri