From owner-freebsd-hackers Thu Nov 8 11:47:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id B744B37B418 for ; Thu, 8 Nov 2001 11:47:12 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id fA8JlAe03457; Thu, 8 Nov 2001 13:47:10 -0600 (CST) (envelope-from tinguely) Date: Thu, 8 Nov 2001 13:47:10 -0600 (CST) From: mark tinguely Message-Id: <200111081947.fA8JlAe03457@web.cs.ndsu.nodak.edu> To: bright@mu.org, jason@macadamian.com Subject: Re: mmap/madvise Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20011108122150.W89342@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Mawdsley asks: > > I am looking for a way to reserve memory, without actually allocating the > > swap space. Alfred Perlstein answers: > Just proceed normally, freebsd does overcommit such that you really > don't need to do anything special to get the results you desire. I assume Jason is writting a userland application, but I cannot tell how he was using the allocated memory. Alfred is correct in that allocated memory is not even physical until needed and only paged back if modified AND space becomes low. Without information of what he was doing, I was trying to read between the lines of his message and wonder if he needs the memory physically there and wired (using mprotect) to prevent the memory from being released. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message