Re: Keeping data from swapping

Article View: comp.sys.next.programmer

Article #72

Back to comp.sys.next.programmer Previous Next

#72

From: Matthew Dillon
Date: Thu, 29 Oct 1992 20:42

40 lines
2111 bytes

In article <1992Oct29.071919.26859@u.washington.edu> zeno@phylo.genetics.washington.edu (Sean Lamont) writes:
>In article <1992Oct28.075558.2721@relief.com> jjfeiler@relief.com writes:
>>I've got a large image that I need to keep all in ram, at all times.  I've
>>used get/setrlimit(RLIMIT_DATA,rtp) calls to set the data limit to the
>>maximum, and that definitely seems to help, but is there any way to wire down
>>pages of ram from an application?  If that isn't possible, would it be
>
>look at kalloc()/kfree()

    From a user program?

    The only get/setrlimit() commands that are implemented are for the
    stack and core dump sizes.	No other parameters are implemented (bug
    report has been sent to bug_next in that regard).  Besides, the
    *rlimit() calls have nothing to do with locking pages in memory nor
    paging.

    The only way I know of to wire pages in memory is through
    kern_serv_wire_range() but it is totally undocumented.  I've never
    tried it myself and it probably wouldn't work from a user process.

    Touching pages probably will not work, the mach paging system doesn't
    have much regard for recent page usage.

    I think you will probably have to get more memory for the machine.

					    -Matt

>--
>Sean T. Lamont 			  |   "Don't oppress me, It's
>zeno@genetics.washington.edu		  |    'computer of color!' "
>lamont@abstractsoft.com		  |_______________________________
>Abstract Software

--

    Matthew Dillon		dillon@Overload.Berkeley.CA.US
    1005 Apollo Way		uunet.uu.net!overload!dillon
    Incline Village, NV. 89451	ham: KC6LVW (no mail drop)
    USA 			Sandel-Avery Engineering (702)831-8000

Technical Details

Message-ID: <dillon.0qiu@overload.Berkeley.CA.US>

Path: arc1-ca.pugleaf.net!sparky!uunet!overload!dillon

References: <1992Oct28.075558.2721@relief.com> <1992Oct29.071919.26859@u.washington.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!overload!dillon
From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Newsgroups: comp.sys.next.programmer
Subject: Re:  Keeping data from swapping
Distribution: world
Message-ID: <dillon.0qiu@overload.Berkeley.CA.US>
References:  <1992Oct28.075558.2721@relief.com> <1992Oct29.071919.26859@u.washington.edu>
Date: 29 Oct 92 12:42:59 PST
Organization: Not an Organization
Lines: 41

Reply to Parent Message