Date: Fri, 24 Dec 1999 10:59:03 -0800 From: "Scott Hess" <scott@avantgo.com> To: "John Polstra" <jdp@polstra.com>, "Michael Sierchio" <kudzu@dnai.com> Cc: <freebsd-core@freebsd.org>, <freebsd-security@freebsd.org> Subject: Re: mlockall() not supported (2nd query) Message-ID: <102201bf4e40$f23c3a10$1e80000a@avantgo.com> References: <XFMail.991224105248.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra <jdp@polstra.com> wrote: > Michael Sierchio wrote: > > mlockall() and munlockall() don't appear to be supported on FreeBSD. > > The most effective way to get them supported is to submit patches. > From a quick look at mlock() in "src/sys/vm/vm_mmap.c", it doesn't > look all that difficult. Does anything bad happen if you mlock() essentially everything? Something like mlock( NULL, (unsigned)-1), but perhaps more targetted than that. That would appear to lock all of the VM pages you already are using, but perhaps not the VM pages you haven't allocated as of yet? Later, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?102201bf4e40$f23c3a10$1e80000a>