HP3000-L Archives

January 1996, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Rick Ehrhart <[log in to unmask]>
Reply To:
Rick Ehrhart <[log in to unmask]>
Date:
Wed, 17 Jan 1996 18:31:38 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Dan Hollis ([log in to unmask]) wrote:
 
>: POSIX.1 does not define a memory locking facility, but POSIX.4 does:
>
>: Lock entire program into memory:
>: int mlockall(int flags);
>: int munlockall(void);
>
>: Lock portions into memory:
>: int mlock(void *address, size_t length);
>: int munlock(void *address, size_t length);
>
>: Reference:
>: Programming for the real world - POSIX.4
>: Bill O. Gallmeister, 548pp.
>: ISBN 1-56592-074-0
>: (C) 1995 O'Reilly & Associates, Inc.
>
>: p.193-200 - "Keeping your memory handy : UNIX and POSIX memory locking"
 
 Realtime OSs tend to implement POSIX.4 before other OSs.  Realtime OSs
 include VxWorks, Linx, and HP-RT.
 
Rick Ehrhart
[log in to unmask]

ATOM RSS1 RSS2