Path: utzoo!attcan!uunet!mcsun!hp4nl!tuegate.tue.nl!eutws1!wsinpdb
From: wsinpdb@eutws1.win.tue.nl (Paul de Bra)
Newsgroups: comp.unix.wizards
Subject: Re: Keeping pages from getting swapped out.
Keywords: swapping, vadvise, sticky bits, torn hair
Message-ID: <1610@tuegate.tue.nl>
Date: 12 Mar 90 10:18:56 GMT
References: <38281@cornell.UUCP> <1588@tuegate.tue.nl> <1856@lzga.ATT.COM>
Sender: news@tuegate.tue.nl
Distribution: comp
Organization: Eindhoven University of Technology, The Netherlands
Lines: 25

In article <1856@lzga.ATT.COM> bogatko@lzga.ATT.COM (George Bogatko) writes:
>> In article <38281@cornell.UUCP> chandra@cs.cornell.edu (Tushar D Chandra) writes:
>uname
>tm600b tm600b 3.2.1 3 3B2
>cd /lib   
>ar tv libc.a | grep plock
>rw-r--r--  5079/  2003    314 May 25 17:44 1987 plock.o
>

Oops, my goof. The call is there allright, and just to make sure I
checked the manual, and it's there too (no, this is not obvious)
and I wrote a small test program and verified that apart from being
there the system call actually works.

Guess I was still sleeping when I claimed that call wasn't there.

Just a word of warning: this call should not be used with large
processes, as this can easily hang the system (my first attempt caused
this). If you suddenly lock most of your memory (I locked 5Mbyte on an
8Mbyte system, which leaves about 1/2Mbyte available to other processes
in my case) the kernel is not able to keep the other processes going.
The whole system just locks up.

Paul.
(debra@research.att.com)