VAX-11 Architecture Reference Manual. Digital Press, May 1982. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Understanding Control Flow - With Concurrent Programming using.. - Buhr (1995) (1 citation) (Correct)
....occur, it is doubtful if this failure situation would arise in practice. Finally, none of the programs using CAS and CAS2 have a bound on the busy waiting; therefore, rule 5 is broken. To deal with the lack of a bound when using CAS and CAS2, and to handle more complex data structures, the VAX [VAX82] computer has instructions to atomically insert and remove a node to from the head or tail of a circular doubly linked list, illustrated approximately by the following C routines: struct links links front, back; bool INSQUE( links entry, links pred ) atomic execution ....
VAX-11 Architecture Reference Manual. Digital Press, May 1982.
File Systems for Clusters from a Protocol Perspective - Braam (Correct)
....DCE DFS InterMezzo performs bulk lookups of directories. 4 Cluster File Systems 4.1 VAXClusters (and Lustre) A true cluster file system was available from Digital Equipment Corporation as early as 1985. VAXClusters have a magnificent architecture, which is extraordinarily well documented in [VAXFS] and [VAXCL] VAXClusters maintain membership based on quorum, which prevents cluster fragmentation. Cluster members can share designated storage devices, residing either in systems or in network attached storage devices. A variety of interconnects can be used. The VAXClusters file system is ....
VMS File System Internals, Kirby McCoy, Digital Press 1990.
Virtual Memory Support for Multiple Page Sizes - Khalidi, Talluri, Nelson.. (1993) (21 citations) (Correct)
....need to examine these areas, and we identify several questions that need to be answered. In particular, we show that providing support for multiple page sizes is not as straightforward as may initially appear. 1 Introduction Virtual memory implementations in current systems such as UNIX [5] VMS [3], NT [13] MACH [2] and Chorus [4] share two basic assumptions regarding physical memory management: There is one page size. This one size may be a multiple of the MMU page size, but there is only one size and it is typically in the range of 512 8K bytes. Physical memory is not very large, ....
VAX/VMS Internals and Data Structures, Lawrence J. Kenah, Ruth E. Goldenberg, and Simon F. Bate, Digital Press, 1988.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC