Date: Wed, 28 Feb 2001 15:08:43 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Peter Dufault <dufault@hda.hda.com>, hackers@FreeBSD.ORG Subject: Re: memorylocked resource (was "Setting memory allocators...") Message-ID: <200102282308.f1SN8hC93566@earth.backplane.com> References: <200102281332.f1SDWPD27689@hda.hda.com> <200102282249.f1SMn6N93107@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
::Along the same lines (matt probably knows the answer) is it
::easy to force paging in and locking down of any memory associated
::with a process so that mlockall(MCL_FUTURE) together with
::an appropriate memorylocked limit gives the requested
::memory semantics? I'd have to check through the specs to see
::how mmap() is supposed to play with mlockall().
::
::Please leave aside most resource management issues
::for now, I'm assuming the main use for this is debugged
::small closed embedded systems, only bring up kickers.
::
::Peter
::Peter Dufault (dufault@hda.com) Realtime development, Machine control,
Heh heh. I didn't answer that very well the first time eh?
In regards to mlockall(MCL_FUTURE). Hmm. Well, you could certainly
implement it inside vm_fault but there are a couple of other cases
where the system manually enters a page into the user's page table.
I haven't researched it but I would not expect it to be difficult.
-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?200102282308.f1SN8hC93566>