Article View: comp.sys.next.programmer
Article #1888Re: Keeping data from swapping
From: Matthew Dillon
Date: Sun, 22 Nov 1992 19:13
Date: Sun, 22 Nov 1992 19:13
26 lines
1601 bytes
1601 bytes
In article <Bx2D2p.71B@research.canon.oz.au> greyham@research.canon.oz.au (Graham Stoney) writes:
>dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>> 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.
>
>I'll be the first to admit that NeXT's documentation, particularly about
>loadable kernel servers is _badly_ lacking, but can we stick to facts when
>we're NeXT-bashing please?
>
>kern_serv_wire_range() is documented: check in NeXT Developer of the Digital
>Librarian. As to whether it will solve the original poster's problem or not...
>
>Graham
Oops! Your right... I had it mapped out because searching through that
section tends to crash librarian. I'll try indexing it again...
-Matt
--
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.0rim@overload.Berkeley.CA.US>Path:
arc1-ca.pugleaf.net!sparky!uunet!overload!dillonReferences:
<1992Oct28.075558.2721@relief.com> <1992Oct29.071919.26859@u.washington.edu> <dillon.0qiu@overload.Berkeley.CA.US> <Bx2D2p.71B@research.canon.oz.au>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.0rim@overload.Berkeley.CA.US> References: <1992Oct28.075558.2721@relief.com> <1992Oct29.071919.26859@u.washington.edu> <dillon.0qiu@overload.Berkeley.CA.US> <Bx2D2p.71B@research.canon.oz.au> Date: 22 Nov 92 11:13:32 PST Organization: Not an Organization Lines: 27