home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!ames!ictv!barry
- From: barry@ictv.com (Barry Lustig)
- Subject: Re: NeXTs running 3.0 *probably* cannot swap to a raw partition
- Message-ID: <1993Jan25.074420.16279@ictv.com>
- Sender: usenet@ictv.com
- Organization: ICTV, Santa Clara, CA (408) 562-9200
- References: <1993Jan21.195003.6023@ictv.com> <CEDMAN.93Jan21153237@capitalist.princeton.edu>
- Date: Mon, 25 Jan 1993 07:44:20 GMT
- Lines: 23
-
- In article <CEDMAN.93Jan21153237@capitalist.princeton.edu> cedman@princeton.edu (Carl Edman) writes:
- Not quite so fast. All you found out that the BSD system call to
- enable swaping is a dummy call. From that one might conclude that the
- NeXT can not swap at all just as quickly as that it can not swap to a
- raw partition. Fortunately that is not so as virtual memory is one of
- the system services which is provided by Mach through the mach_swapon
- system call and not BSD on a NeXT. And mach_swapon is _not_ a dummy
- call. Careful analysis of this call and its subroutines might reveal
- that indeed it is impossible to swap to a raw partition (as I believe
- it is). This analysis is left as an exercise to the reader.
-
- Carl Edman
-
-
- As I mentioned to Carl in a mail message, I did look at mach_swapon
- as well. As far as I can tell, mach_swapon uses the vnode pager code.
- This provides for paging to a file, not to a raw device.
-
- One can also look at the virtual memory sub-system of 386bsd or
- Berkeley net-2. Both of them use the mach virtual memory system.
-
- barry
- --
-