From owner-freebsd-hackers Tue Oct 2 22:52:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id ECD1537B405 for ; Tue, 2 Oct 2001 22:52:12 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f935q5j63360; Tue, 2 Oct 2001 22:52:05 -0700 (PDT) (envelope-from dillon) Date: Tue, 2 Oct 2001 22:52:05 -0700 (PDT) From: Matt Dillon Message-Id: <200110030552.f935q5j63360@earth.backplane.com> To: Maxime Henrion Cc: Dwayne , freebsd-hackers@FreeBSD.ORG Subject: Re: Memory allocation question References: <3BBA29C0.5E125DAF@xwave.com> <20011002233851.A1317@nebula.cybercable.fr> 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 Don't use mlock(). Use SysV Shared memory segments. If you tell the kernel to use physical ram for SysV shared memory (kern.ipc.shm_use_phys=1) then any shm segments you allocate (see manual pages for shmctl, shmget, and shmat) will reside in unswappable shared memory. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message