From owner-freebsd-hackers Tue Oct 2 14:39: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id 8A48237B407 for ; Tue, 2 Oct 2001 14:39:01 -0700 (PDT) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id f92Lcp518844; Tue, 2 Oct 2001 23:38:51 +0200 (CEST) (envelope-from mux) Date: Tue, 2 Oct 2001 23:38:51 +0200 From: Maxime Henrion To: Dwayne Cc: freebsd-hackers@freebsd.org Subject: Re: Memory allocation question Message-ID: <20011002233851.A1317@nebula.cybercable.fr> References: <3BBA29C0.5E125DAF@xwave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BBA29C0.5E125DAF@xwave.com> User-Agent: Mutt/1.3.22.1i 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 Dwayne wrote: > I'm creating an app where I want to use memory to store data so I > can get at it quickly. The problem is, I can't afford the delays that > would occur if the memory gets swapped out. Is there any way in FreeBSD > to allocate memory so that the VM system won't swap it out? > I think mlock(2) is what you want. Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message