Date: Tue, 2 Oct 2001 22:52:05 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: Maxime Henrion <mux@qualys.com> Cc: Dwayne <Dwayne.MacKinnon@xwave.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Memory allocation question Message-ID: <200110030552.f935q5j63360@earth.backplane.com> References: <3BBA29C0.5E125DAF@xwave.com> <20011002233851.A1317@nebula.cybercable.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
:
: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110030552.f935q5j63360>