Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!mordor!lll-crg!seismo!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: The POSIX file system
Message-ID: <6224@ut-sally.UUCP>
Date: Tue, 4-Nov-86 12:22:50 EST
Article-I.D.: ut-sally.6224
Posted: Tue Nov  4 12:22:50 1986
Date-Received: Wed, 5-Nov-86 06:23:18 EST
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 24
Approved: jsq@sally.utexas.edu

From: garry@tcgould.tn.cornell.edu (Garry Wiegand)
Date: Tue, 4 Nov 86 00:45:47 EST
Organization: Cornell Engineering && Flying Moose Graphics

In a recent article jbs@eddie.mit.edu (Jeff Siegal) wrote:
>In article <6206@ut-sally.UUCP> guy@sub.com (Guy Harris)
>>[...]  I believe the latest descendents of MERT, and VMS, have moved the
>>file system back into the kernel for performance reasons.
>
>Quite far off, actually (at least in the case of VMS).  Current
>versions of VMS have replaced the disk filesystem ACP (which
>previously was a separate process) with the XQP, a separate instance
>of which exists in _each_process_ (the code is shared).  [...]

Sorry to quibble, but the original posting was accurate. There is now
a piece of the kernel which Dec has labelled the "XQP". The code runs
in the context of a user-process, as is indistinguishably true of every
other system service. The stated reason for making the move was increased
performance. That the cluster software was easier to write was probably
a bonus.

garry wiegand   (garry%cadif-oak@cu-arpa.cs.cornell.edu)

Volume-Number: Volume 8, Number 32