Apparatus and method for hardware-based file system
Patent 7337190 Issued on February 26, 2008.
Estimated Expiration Date: November 1, 2022.
Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.
A hardware-based file system includes multiple linked sub-modules that perform functions ancillary to client data handling. Each sub-module is associated with a metadata cache. A doubly-rooted structure is used to store each file system object at successive checkpoints. Metadata is stored within an object and/or as a separate object. Provisions are made for allocating sparse objects. A delayed write feature is used for writing certain objects into non-volatile storage. Checkpoints can be retained as read-only versions of the file system. Modifications to the file system are accomplished without affecting the contents of retained checkpoints. The file system can be reverted to a retained checkpoint. Multiple file servers can be interconnected as a cluster, and each file server stores requests from another file server. Interconnections between file servers can be dynamically modified. A distributed locking mechanism is used to control access to file system objects stored by the file servers.
Claims
What is claimed is:
1. A file server system for accessing and utilizing a data storage system, the file server system including a network subsystem for receiving and responding to file servicerequests over a network and further including a file subsystem, in communication with the network subsystem, for satisfying the file service requests, the file subsystem comprising: a. a data bus arrangement, in communication with the network subsystemand the data storage system, for providing data to be stored in the data storage system and for retrieving data from the data storage system; b. a plurality of linked sub-modules, wherein the linked sub-modules as a group are in communication with acontrol input for receiving file service requests and a control output for responding to file service requests and process such service requests and generate responses thereto over the control output, each sub-module configured to perform a distinct setof operations pertinent to processing of such file service requests; wherein the control input and the control output are distinct from the data bus arrangement; and c. a plurality of metadata memory caches, each metadata memory cache associated with acorresponding sub-module for storing metadata pertinent to operations of such sub-module.
2. A file server system for accessing and utilizing a data storage system, the file server system including a network subsystem for receiving and responding to file service requests over a network and further including a file subsystem, incommunication with the network subsystem, for satisfying the file service requests, the file subsystem comprising: a. a data bus arrangement, in communication with the network subsystem and the data storage system, for providing data to be stored in thedata storage system and for retrieving data from the data storage system; b. a plurality of linked sub-modules, wherein the linked sub-modules as a group are in communication with a control input for receiving file service requests and a control outputfor responding to file service requests and process such service requests and generate responses thereto over the control output, each sub-module configured to perform a distinct set of operations pertinent to processing of such file service requests; and c. a plurality of metadata memory caches, each metadata memory cache associated with a corresponding sub-module for storing metadata pertinent to operations of such sub-module without storage of file content data.
3. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage systemand a file sub-module for managing data structure associated with file attributes.
4. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system, afile sub-module for managing data structure associated with file attributes, and a directory sub-module for handling directory management for the file sub-module.
5. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules include an object store sub-module for causing storage and retrieval of file system objects in the storage system and a free space allocationsub-module for retrieving and updating data pertinent to allocation of space in the data storage system.
6. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system, afile sub-module for managing data structure associated with file attributes, a directory sub-module for handling directory management for the file sub-module, and a tree sub-module for handling directory lookups for the directory sub-module.
7. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system, afile sub-module for managing data structure associated with file attributes, a directory sub-module for handling directory management for the file sub-module, and a tree sub-module for handling directory lookups for the directory sub-module, wherein thedirectory sub-module associates each file with a randomized value, and wherein the tree sub-module manages a logical tree structure based upon the randomized values from the directory sub-module.
8. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system, afile sub-module for managing data structure associated with file attributes, a directory sub-module for handling directory management for the file sub-module, and a tree sub-module for handling directory lookups for the directory sub-module, wherein thedirectory sub-module associates each file with a randomized value comprising a cyclic redundancy checksum (CRC) of a file name associated with the file, and wherein the tree sub-module manages a logical tree structure based upon the randomized valuesfrom the directory sub-module.
9. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system, afile sub-module for managing data structure associated with file attributes, a directory sub-module for handling directory management for the file sub-module, and a tree sub-module for handling directory lookups for the directory sub-module, wherein thedirectory sub-module associates each file with a randomized value, and wherein the tree sub-module associates each randomized value with an index into the logical tree structure and uses the randomized values to access the logical tree structure.
10. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,a file sub-module for managing data structure associated with file attributes, a directory sub-module for handling directory management for the file sub-module, and a tree sub-module for handling directory lookups for the directory sub-module, whereinthe directory sub-module associates each file with a randomized value, and wherein the directory sub-module maintains a list of files that are associated with the same randomized value and uses the list of files to access files associated with the samerandomized value.
11. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system.
12. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system, and wherein the non-volatile storage processing sub-module is operably coupled to store the file system request data in the non-volatile storage at the request of a processor for recovery from afailure.
13. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system, and wherein the non-volatile storage processing sub-module is operably coupled to store the file system request data in the non-volatile storage at the request of a processor for recovery from afailure and to send an acknowledgment to the processor confirming storage of the file system request data in the non-volatile storage.
14. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system, and wherein the non-volatile storage processing sub-module is operably coupled to receive file system request data from another file server via an interface and to store the file system requestdata from the other file server in the non-volatile storage.
15. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system, and wherein the non-volatile storage processing sub-module is operably coupled to send the file system request data to another file server via an interface for non-volatile storage of the filesystem request data by the other file server.
16. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system.
17. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure in its associated metadata cache for each file system object to be stored in the storage system.
18. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system, the file system objects comprising files, directories, and file attributes.
19. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system and effectuates storage of the file structures into the storage system at various checkpoints.
20. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system and effectuates storage of the file structures into the storage system when initiated by an external processor.
21. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for causing storage and retrieval of file system objects in the storage system,and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system and effectuates storage of the file structures into the storage system when a predetermined amount of time has elapsed sincea last storage of the file structures into the storage system.
22. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storage processing sub-module with associated non-volatile storage for storing file systemrequest data for subsequent storage in the storage system and an object store sub-module for causing storage and retrieval of file system objects in the storage system, and wherein the object store sub-module maintains a file structure for each filesystem object to be stored in the storage system and effectuates storage of the file structures into the storage system when a portion of the non-volatile storage used for storage of the file system request data is becoming full.
23. A file server according to any of claims 1 or 2, further comprising a sector cache for maintaining sector-level information about the storage system, wherein the plurality of linked sub-modules are hierarchically arranged and include anobject store sub-module for causing storage and retrieval of file system objects in the storage system, and wherein the object store sub-module maintains a file structure for each file system object to be stored in the storage system and effectuatesstorage of the file structures into the storage system when the sector cache is becoming full.
24. A file server according to any of claims 1 or 2, further comprising a controller external to the plurality of linked sub-modules, wherein the plurality of linked sub-modules are hierarchically arranged and include a non-volatile storageprocessing sub-module with associated non-volatile storage for storing file system request data for subsequent storage in the storage system, a file sub-module for managing data structure associated with file attributes, a directory sub-module forhandling directory management for the file sub-module, a tree sub-module for handling directory lookups for the directory sub-module, an object store sub-module for maintaining a file structure for each file system object to be stored in the storagesystem and for effectuating storage of the file structures into the storage system at various checkpoints, and a free space allocation sub-module for retrieving and updating data pertinent to allocation of space in the data storage system, and wherein:the controller sends a number of file system requests to the non-volatile storage processing sub-module and subsequently sends a checkpoint inquiry command to the non-volatile storage processing sub-module to initiate storage of the file structures intothe storage system for a checkpoint, the checkpoint inquiry command including a checkpoint number for the checkpoint; the non-volatile storage processing sub-module stores the number of file system requests in the non-volatile storage, optionally sendsthe number of file system requests to another file server via an interface for non-volatile storage of the number of file system requests by the other file server, sends the number of file system requests to the file sub-module, and subsequently sends acheckpoint command to the file sub-module; the file sub-module processes the number of file system requests, and, upon receiving the checkpoint command from the non-volatile storage processing sub-module, waits for certain operations to complete throughthe remaining sub-modules and then sends a checkpoint command to the directory sub-module; the directory sub-module receives the checkpoint command from the file-sub-module and sends a checkpoint command to the tree sub-module; the tree sub-modulereceives the checkpoint command from the directory sub-module and sends a checkpoint command to the object store sub-module; the object store sub-module receives the checkpoint command from the tree sub-module and sends a checkpoint inquiry to the freespace allocation sub-module; the free space allocation sub-module receives the checkpoint inquiry from the object store sub-module, completes any operations necessary for the checkpoint including operations initiated subsequent to receiving thecheckpoint inquiry, and then sends a response to the object store sub-module; and the object store sub-module causes the file system objects to be written to the storage system, including an updated objects lists indicating any and all objects that havebeen modified since a last checkpoint.
25. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system.
26. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, each node comprising at least one of: a pointer to another node; and a data block descriptor.
27. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, each node comprising a checkpoint number indicating a checkpoint during which the node was created.
28. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint.
29. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint, the two root nodes stored in adjacent sectors in thestorage system.
30. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint, each root node comprising at least one of: an objecttype for indicating whether the file system object is a file or a directory; an object length for indicating the number of data blocks associated with the file system object; a reuse count indicating the number of time the root node has been used; apointer to a previous instantiation of the root node; a pointer to a subsequent instantiation of the root node; at least one a data block descriptor including a pointer to a data block, a checkpoint number indicating a relative time the data block wascreated, and an indicator to indicate whether the data block is zero or non-zero; and file attributes (enode).
31. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint and at least one direct node including at least one adata block descriptor.
32. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint and at least one direct node including at least one adata block descriptor, at least one of the root nodes comprising a pointer to the direct node.
33. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint and at least two indirect nodes, each indirect nodeincluding at least one pointer to one of: another indirect node; and a direct node.
34. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the plurality of nodes comprising at least two root nodes for storing information for a first and a second checkpoint and at least two indirect nodes, at least one of the rootnodes comprising a pointer to an indirect node, the indirect node comprising pointers to at least two direct nodes.
35. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the file structure comprising an indicator for each data block associated with the file system object to indicate whether the data block is zero or non-zero.
36. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, the file structure comprising an indicator for node and data block to indicate whether each node and data block has been created.
37. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system, and wherein the object store sub-module is operably coupled to create nodes and data blocks as necessary to accommodate file system write requests and to set an indicator foreach node and data block to indicate that the node or data block has been created.
38. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure comprising a plurality of nodes and at leastone data block for each file system object to be stored in the storage system and a free space allocation sub-module for retrieving and updating data pertinent to allocation of space in the storage system, and wherein the object store sub-module createsa data block by allocating space for the data block from the free space allocation sub-module.
39. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure for each file system object to be stored in thestorage system, and wherein the object store sub-module is operably coupled to maintain a transaction log.
40. A file server according to any of claims 1 or 2, wherein the plurality of linked sub-modules are hierarchically arranged and include an object store sub-module for maintaining a file structure for each file system object to be stored in thestorage system and a transaction log, and wherein the object store sub-module is operably coupled to store the transaction log and the file structure in the storage system from time to time.
41. A file server according to any of claims 1 or 2, wherein at least one of the plurality of sub-modules comprises dedicated hardware.
42. A file server according to any of claims 1 or 2, wherein at least one of the plurality of sub-modules comprises a dedicated processor.
43. A file server according to any of claims 1 or 2, wherein the storage system comprises at least one of: magnetic storage; magneto-optical storage; and optical storage.
Other References
Boosting Network Server Adapter Performance by 800%, Technology White Paper, Alacritech, Inc., 2000, 14 pages.
Alacritech 100x4 Quad-Port Server Adapter, Alacritech, http://www.alacritech.com/html/4port.html, printed Aug. 28, 2000, 2 pages.
Alacritech 100x4 Quad-Port Server Adapter, Alacritech, Data Sheet, 1 page.
Boosting Network Server Adapter Performance by 800%, Technology White Paper, Alacritech, Inc., http://www.alacritech.com/html/pci—traffic.html, printed Aug. 8, 2000, 2 pages.
The Case for Storage Virtualization Using Intelligent Routers, White Paper, Crossroads Systems, Inc, Doc. No. XP-002200766, 2001, pp. 1-10.
Sun Cluster System Administration Guide for Solaris OS, Sun Microsystems, Inc., Part No. 819-0580-10, printed online on Aug. 26, 2005, 2005.
Solstice HA 1.2 Software Administration Guide, Sun Microsystems, Inc., Appendix C, 1996.
The Next Step In Server Load Balancing, White Paper, Alteon WebSystems, Inc., Nov. 1999.
Davis, R., VAXCluster Principles, Digital Press, ISBN 1-55558-112-9, 1993.
Mullender, S., Distributed Systems, ACM Press New York, ISBN 0-201-62427-3, Second Edition, 1993.
Pfister, G., In Search of Clusters, Prentice Hall PTR, ISBN 0-13899709-8, Second Edition, 1998.
Sun™ Cluster 3.0 Concepts, Sun Microsystems, Inc., Part No. 806-1424-10, Nov. 2000.
Norbert Wienold, Primary Examiner for the Examining Division, Communication Pursuant to Article 96(2) EPC, EPO Application No. 03 781 504.0-2201, Nov. 17, 2006, 5 pages.
Leach et al., The File System of an Integrated Local Network, Proceedings of the 1985 ACM Computer Science Conference—Agenda for Computing Research, The Challenge for Creativity, Mar. 12-14, 1985, pp. 309-324.
Cheriton et al., The VMP Multiprocessor: Initial Experience, Refinements and Performance Evaluation, IEEE, Feb. 1988, 36 pages.
Cheriton, The V Distributed Operating System: Principles and Principal Experiences, Dept. of Computer Science, Stanford University, Apr. 1986, pp. 1-3.
Cheriton, The Unified Management of Memory in the V Distributed System, Dept. of Computer Science, Stanford University, Report No. STAN-CS-88-1192, Aug. 1988, pp. 1-24.
Cheriton, UIO: A Uniform I/O system Interface for Distributed Systems, Dept. of Computer Science, Stanford University, Report No. STAN-CS-86-1134, Nov. 1986, pp. 1-30.
Cheriton et al., Software-Controlled Caches in the VMP Multiprocessor, Dept. of Computer Science, Stanford University, Report No. STAN-CS-86-1105, Mar. 1986, pp. 1-12.
Cheriton, Sirpent™: A High-Performance Internetworking Approach, Dept. of Computer Science, Stanford University, Report No. STAN-CS-89-1273, Jul. 1989, 17 pages.
Cheriton et al., Process Identification in Thoth, Dept. of Computer Science, The University of British Columbia, Technical Report 79-10, Oct. 1979.
Cheriton et al., Performance of the V Storage Server: A Preliminary Report, Proceedings of the 1985 ACM Computer Science Conference—Agenda for Computing Research: The Challenge for Creativity, Mar. 12-14, 1985, pp. 302-308.
Cheriton et al., One-to-Many Interprocess Communication in the V-System, Dept. of Computer Science, Stanford University, Report No. STAN-CS-84-1011, Aug. 1984.
Chorafas, Designing and Implementing Local Area Networks, McGraw-Hill Book Company, New York, pp. 214-229.
Almes, Understanding and Exploiting Distribution, Dept. of Computer Science, Rice Univ., Technical Report 85-12, Feb. 1985.
Almes, The Impact of Language and System on Remote Procedure Call Design, Dept. of Computer Science, Rice Univ., Technical Report 85-26, Oct. 23, 1985.
Marshall, Auspex NFS Server Separates NFS From Unix Kernel to Increase I/O, Infoworld, Oct. 16, 1989, pp. 40 and 42.
Mason, Distributed Processing: The State of the Art, Byte, Nov. 1987, pp. 291-297.
Lobelle, Integration of Diskless Workstations in UNIX United, Software—Practice & Experience, vol. 15(10), Oct. 1985, pp. 997-1010.
Lazowska et al., File Access Performance of Diskless Workstations, Dept. of Computer Science, Stanford University, Report No. STAN-CS-84-1010, Jun. 1984, 1-26.
Hurwicz, Superservice with a smile, Network World, Feb. 12, 1990, pp. 43-46.
Haas et al., Blazenet: A Phototonic Implementable Wide-Area Network, Dept. of computer Science, Stanford University, Report No. STAN-CS-87-1185, Oct. 1987, pp. 1-21.
Greenstein, A dedicated server may help cure your network performance headaches, Networking Management, Apr. 1991, pp. 75-79.
Finlayson et al., Log Files: An Extended File Service Exploiting Write-Once Storage, Dept. of Computer Science, Stanford University, Report No. STAN-CS-87-1177, Sep. 1987, pp. 1-12.
Zwaenepoel, Implementation and Performance of Pipes in the V-System, Dept. of Computer Science, Rice Univ., COMP TR85-14, Mar. 1985.
Weinberger, Distributed File Access, ACM Thirteenth Annual Computer Science Conference, New Orleans, LA, Mar. 1985, pp. 299-301.
Shoens et al., Research Report Amoeba Project, IBM Research Laboratory, San Jose, CA, RJ 4465 (48253), Oct. 12, 1984.
Row et al., Operating System Extensions Link Disparate Systems, Computer Design, Jul. 1984, pp. 171-183.
Hindin, Micro Operating Systems Yield Mixed Blessings, Computer Design, Jul. 1984, pp. 155-170.
Row, LAN Software Links Diverse Machines, OS's, Mini-Micro Systems, Sep. 1985, 4 pages.
Cheriton et al., Network Measurement of the VMTP Request-Response Protocol in the V Distributed System, Dept. of Computer Science, Stanford Univ., Report No. STAN-CS-87-1145, Feb. 1987.
Cheriton, Multi-Process Structuring and the Thoth Operating System, Dept. of Computer Science, Univ. of British Columbia, Mar. 1979.
Cheriton et al., Multi-Level Shared Caching Techniques for Scalability in VMP-MC, Dept. of Computer Science, Stanford Univ., Report No. STAN-CS-89-1266, May 1989.
Cheriton et al., Host Groups: A Multicast Extension for Datagram Internetworks, Dept. of Computer Science, Stanford Univ., Report No. STAN-CS-85-1058, Jul. 1985.
Cheriton, Exploiting Recursion to Simplify RPC Communication Architectires, Dept. of Computer Science, Stanford Univ., Report No. STAN-CS-88-1213, Jun. 1988.
Cheriton et al., The Distributed V Kernel and its Performance for Diskless Workstations, Association for Computing Machinery, Jul. 1983, pp. 129-140.
Cheriton et al., Distributed Process Groups in the V Kernel, ACM Transactions on Computer Systems, vol. 3, No. 2, May 1985, pp. 77-107.
Cheriton Distributed I/O using an Object based Protocol, Dept. of Computer Science, Univ. of British Columbia, Technical Report 81-1, Jan. 1981.
Cheriton, Dissemination-Oriented Communication Systems, Computer Science Dept., Stanford Univ., 1992, pp. 1-8.
Cheriton et al., A Decentralized Naming Facility, Dept. of Computer Science, Stanford Univ., Feb. 1986, pp. 1-28.
Cheriton et al., Uniform Access to Distributed Name Interpretation in the V-System, Computer Science Dept., Stanford Univ., The 4th International Conference on Distributed Computing Systems, May 14-18, 1984, San Francisco, IEEE Computer Society, pp. 290-297.
Vuillemin et al., Programmable Active Memories: Reconfigurable Systems Come of Age, IEEE Transactions on Very Large Scale Integration (VLSI) Systems, vol. 4, No. 1, Doc. No. 1063-8210/96, Mar. 1996, 14 pages.
Ponomarev et al., A Comparative Study of Some Network Subsystem Organizations, Department of Computer Science, State University of New York, IEEE, Doc. No. 0-8186-9194-8/98, 1998, 8 pages.
Memoranddum & Order Re: Cross-Motions for Summary Judgement of Infringement and Noninfringement; Defendant's Motion for Summary Judgement on Damages, Network Appliance, Inc. v. BlueArc Corp., Case No. C 03-5665 MHP, Jun. 27, 2005, 25 pages.
Memorandum & Order Re: Plantiff's Motions for Summary Judgement of Infringement; Defendant's Motions for Summary Judgement of Noninfringement, Network Appliance, Inc. v. BlueArc Corp., Case No. C 03-5665 MHP, May 16, 2005, 27 pages.
Chau, V., Technical Brief: Titan & Alacritech iSCSI Accelerator on Microsoft Windows®, BlueArc Corporation, 2005, pp. 1-21.
SiliconServer White Paper, BlueArc Corporation, 2002, pages 1-18.
Williamson, et al., An Overview of the VMTP Transport Protocol, Computer Science Department, Stanford University, IEEE, Jun. 1989, pp. 415-420.
Cheriton, et al., VMTP as the Transport Layer for High-Performance Distributed Systems, IEEE Communications Magazine, Jun. 1989, pp. 37-44.
Cheriton, D., VMTP: A Transport Protocol for the Next Generation of Communication Systems, Computer Science Department, Stanford University, ACM, 1986, pp. 406-415.
Cheriton, D., Problem-oriented Shared Memory: A Decentralized Approach to Distributed System Design, Computer Science Department, Stanford University, IEEE Computer Society, The 6th International Conference on Distributed Computing Systems, May 19-23, 1986, pp. 190-197.
Spector et al., Support for Distributed Transactions in the TABS Prototype, Dapartment of Computer Science, Carnegie-Mellon University, IEEE 1984 Fourth Symposium on Reliability in Distributed Software and Database Systems, Oct. 15-17, 1984, pp. 186-206.
Malcolm et al., Coping with Network Partitions an Processor Failures in a Distributed System, Software Portability Laboratory, University of Waterloo, IEEE 1984 Fourth Symposium on Reliability in Distributed Software and Database Systems, Oct. 15-17, 1984, pp. 36-44.
Nowicki, W., Partitioning of Function in a Distributed Graphics System, Department of Computer Science, Stanford University, Mar. 1985, pp. 1-136.
Hall et al., The Sun Technology Papers, Sun Microsystems, Inc., Sun Technical Reference Library, 1990, pp. 1-239.
Hall et al., X: A Window System Standard for Distributed Computing Environments, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 46-50.
Perlmutter, P., Small Computer System Interface, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 39-45.
Wagner, K., Discless System Configuration Tasks, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 37-39.
Scott, et al., Boot Mechanism for Discless HP-UX, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 33-36.
Randel, A., Crash Detection and Recovery in a Discless HP-UX System, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 27-32.
Gutierrez et al., The Design of Network Functions for Discless Clusters, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 20-26.
Hwang et al., Discless Program Execution and Virtual Memory Management, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 15-20.
Bartlett et al., A Discless HP-UX System, Hewlett-Packard Journal, Oct. 1988, vol. 39, No. 5, pp. 10-14.
Shipley, M., The Virtual Home Environment, Hewlett-Packard Company, UniForum 1988 Conference Proceedings—Dallas, Texas, Feb. 8-11, 1988, pp. 117-181.
Kabashima et al., Implementing the Protocol Validation System in Sun Workstations, Kokusai Denshin Denwa Co., Ltd., UniForum 1988 Conference Proceedings—Dallas, Texas, Feb. 8-11, 1988, pp. 81-93.
Prestoserve Beta Test Customer Report, 1 page.
Presto Disk™ Network File System Server Accelerator, Legato Systems, Inc., 2 pages.
PrestoServe™ Network File System Server Accelerator, Legato Systems, Inc., 4 pages.
Welch et al., Pseudo-File-Systems, Computer Science Division, Electrical Engineering and Computer Sciences, University of California, Report No. UCB/CSD 89/499, Apr. 1989, pp. 1-12.
Edler et al., Considerations for Massively Parallel UNIX Systems on the NYU Ultracomputer and IBM RP3, Ultracomputer Research Laboratory Courant Institute of Mathematical Sciences, USENIX Technical Conference, Winter 1986, pp. 193-210.
Jacobs, H., A User-tunable Multiple Processor Scheduler, Alliant Computer Systems, USENIX Technical Conference, Winter 1986, pp. 183-191.
Test et al., Multi-Processor Management In the Concentrix Operating System, Alliant Computer Systems Corporation, USENIX Technical Conference, Winter 1986, pp. 172-182.
Probert et al., A Straightforward Implementation of 4.2BDS on a High-performance Multiprocessor, Culler Scientific Systems Corporation, USENIX Technical Conference, Winter 1986, pp. 140-156.
Straathof et al., UNIX Scheduling for Large Systems, Department of Computer Science University of Maryland, USENIX Technical Conference, Winter 1986, pp. 111-139.
Gosling, J., SunDew: A Distributed and Extensible Window System, Sun Microsystems, USENIX Technical Conference, Winter 1986, pp. 98-103.
Sun Microsystems Inc. and Culler Scientific Systems Announce Joint Sales and Marketing Venture, PR Newswire, Oct. 25, 1985, 1 page.
Culler Announces First Personal Supercomputer, The Journal Record, May 7, 1986, 1 page.
Lichtenstein, W., The Architecture of the Culler 7, Culler Scientific Systems Corporation, IEEE computer Society Compcon Spring '86, Mar. 3-6, 1986, pp. 467-470.
Walsh, et al., Overview of the Sun Network File System, Sun Microsystems, Inc., USENIX Association Conference Winter 1985, pp. 117-124.
Uttal, et al., Transparent Integration of UNIX and MS-DOS, Locus Computing Corporation, USENIX Association Conference Winter 1985, pp. 104-116.
Requa, J., UNIX Kernel Networking Support and the Lincs Communications Architecture, Lawrence Livermore National Laboratory, USENIX Association Conference Winter 1985, pp. 98-103.
Finger, et al., A Multi-CPU Version of the Unix Kernel of Technical Aspects and Market Need, MASSCOMP Engineering, USENIX Association Conference Winter 1985, pp. 11-21.
Lyon et al., All the Chips that Fit, Sun Microsystems, Inc. USENIX Association Conference Summer 1985, pp. 557-561.
Cole, et al., An Implementation of an Extended File System for UNIX, MASSCOMP, USENIX Association Conference Summer 1985, pp. 131-149.
Ferrin, T., A Recipe for Establishing Point-to-Point TCP/IP Network Links with 4.2 BSD UNIX, Computer Graphics Laboratory School of Pharmacology, University of California, USENIX Association Conference Summer 1985, pp. 113-118.
Chang, J., SunNet, Sun Microsystems, Inc., USENIX Association Conference Summer 1985, pp. 71-78.
Hitz et al., A Mail File System for Eighth Edition UNIX, Computer Science Department, Princeton University, USENIX Association Conference Proceedings, 1986 Summer, pp. 28-37.
Ghodssi et al., A Global Optimizer for Sun FORTRAN, C & Pascal, Sun Microsystems, Inc., USENIX Association Conference Proceedings, 1986 Summer, pp. 318-334.
Hughes, R., The Transparent Remote File System, Integrated Solutions, Inc., USENIX Association Conference Proceedings, 1986 Summer, pp. 306-317.
Rosen et al., NFS Portability, The Instruction Set Ltd., USENIX Association Conference Proceedings, 1986 Summer, pp. 299-305.
Gould, E., The Network File System Implemented on 4.3BSD, MT XINU, USENIX Association Conference Proceedings, 1986 Summer, pp. 294-298.
Rodriguez et al., The Generic File System, ULTRIX Engineering and Advanced Development Group, Digital Equipment Corporation, USENIX Association Conference Proceedings, 1986 Summer, pp. 260-269.
Rifkin et al., RFS Architectural Overview, AT&T, USENIX Association Conference Proceedings, 1986 Summer, pp. 248-259.
Taylor et al., Secure Networking in the Sun Environment, Sun Microsystems, Inc., USENIX Association Conference Proceedings, 1986 Summer, pp. 28-37.
Associated Computer Consultants, Protocol package accesses transparently, Computer Design, May 1983, pp. 30, 32 and 34.
Williams, T., Serial buses provide small area networks between system ICs, and modules, Computer Design, Jan. 1983, p. 40.
Coulouris et al., Distributed Systems, Concepts and Design, International Computer Science Series, 1988, pp. 1-366.
Scott, K., IBM Software Lets Host Act as NFS File Server, Connectivity, Aug. 29, 1988, 1 page.
West et al., Local networks for computer communications, IFIP Working Group 6.4, International Workshop on Local Networks, Aug. 27-29, 1980, North-Holland Publishing Company, 1980, 20 pages.
Row, J., LAN Software Links Diverse Machines, OS's, Mini-Micro Systems, Sep. 1985, 4 pages.
Poor, V., The Concept of Attached Processing and Attached Resource Computer Systems, Datapoint Corporation, pp. 110-116.
Israel et al., Eliminating Data Copies in UNIX-based NFS Servers, UniForum 1989 Conference Proceedings, San Francisco, pp. 261-272.
Fong et al., Build a high-performance SCSI bridge controller, Electronic Design, Jul. 9, 1987, pp. 107-111.
Martin, S., IC vendors keep pace with peripheral control requirements, Computer Design, Jun. 15, 1987, 9 pages.
Martin, S., Peripheral controller ICs gain speed and flexibility, Computer Design, Jun. 15, 1988, pp. 41-45.
McGraw, T., New hardware cuts price of graphics power, Government Computer News, vol. 7, No. 8, Apr. 15, 1998, 2 pages.
Computer Design Special Report: Advanced Digital ICs, A PennWell Publication, Feb. 1983, 7 pages.
Nowicki, B., Transport Issues in the Network File System, Sun Microsystems, Mar. 8, 1989, 5 pages.
Culler et al., Parallel Computer Architecture, A Hardware/Software Approach, Morgan Kaufmann Publishers, Inc., Chapter 1, 1999, pp. 25-42.
Hennessy et al., Computer Organization and Design The Hardware/Software Interface, Morgan Kaufmann Publishers, Inc., Chapters 8 and 9, 1998, pp. 655-740, plus Glossary.
Taylor et al., VLSI Node Processor Architecture for Ethernet, IEEE Journal on Selected Areas in Communications, vol. SAC-1, No. 5, Nov. 1983, pp. 733-739.
Strang, C., A New Family of SCSI Protocol Controller Chips, Designed with Modular Standard Cell Approach, Texas Instrument, Inc., pp. 119-124.
Bowman, R., Multitasking keys SCSI control of large SMD-compatible disks, Electronic Design, Jun. 25, 1987, pp. 89-94.
Jovanov et al., Hardware Implementation of Some DBMS Functions using SPR, System Sciences, 1992, Jan. 7, 1992, pp. 328-337.
Coronminas et al., A VLSI Implementation of a SMDS Attachment Unit over an ICI interface, Melecon '96, XP-001001248, May 13, 1996, pp. 373-376.
Cardinal, D., File Server Offers Transparent Access to Design Tools, Computer Design, Jun. 1985, 5 pages.
Ennis, G., The LocalNet/PC Protocols: An Overview, Sytek, Incorporated, Aug. 3, 1984, 22 pages.
Abstract—Communications Controller for bi-directional data transfer includes separate bus segments operating to interconnect microprocessor with communication network and arbitration logic, Derwent Publications Ltd, London, England, 1986, 1 page.
Zwaenepoel, W., Message Passing on a Local Network, Department of Computer Science, Stanford University, Report No. STAN-CS-85-1083, Oct. 1985, pp. 1-101.
RPC: Remote Procedure Call Protocol Specification Version 2, Internet Engineering Task Force RFC 1057, Jun. 1988, 24 pages.
XDR: External Data Representation Standard, Internet Engineering Task Force RFC 1014, Jun. 1987, 19 pages.
Internet Protocol DARPA Internet Program Protocol Specification, Internet Engineering Task Force RFC 791, Sep. 1981, pp. 1-49.
Cheriton, D., VMTP: Versatile Message Transaction Protocol—Protocol Specification, Internet Engineering Task Force RFC 1045, Feb. 1988, 128 pages.
Draves, R., A Revised IPC Interface, USENIX Association, Mach Workshop, pp. 101-121.
van Renesse et al., Connecting RPC-Based Distributed Systems Using Wide-Area Networks, Dept. of Mathematics and Computer Science, Vrije Universiteit, Amsterdam, The Netherlands, pp. 108-119.
van Renesse et al., Wide-Area communication under Amoeba, Vrije Universiteit, Amsterdam, pp. 1-12.
Computers & peripherals—Small unit has multiprocessor architecture, Electronics, Feb. 9, 1984, p. 161.
Tanenbaum, et al., Research Issues in Distributed Operating Systems, Dept. of Mathematics and Computer Science, Vrije Universiteit, Amsterdam, The Netherlands, 10 pages.
Cheriton et al., V-System 6.0 Reference Manual including Part II: V Programming and Part III: V Servers, Jun. 20, 1986, pp. 1-1 to 46-1.
McLeod, B., Sacrifices to Ra or Learning to Administer a Sun Network, EUUG Autumn '88—Cascais, Oct. 3-7, 1988, pp. 249-252.
The period 1986-1990 Datacommunication and the PC local area network, online http://www.tno.nl.instit.fel/museum/computer/en/comp863E.html, printed Aug. 11, 2003, 3 pages.
Marzullo et al., Supplying High Availability with a Standard Network File System, Department of Computer Science, Cornell University, IEEE, 1988, pp. 447-453.
Cheriton et al., Thoth, a Portable Real-Time Operating System, Communications of the ACM, vol. 22, No. 2, Feb. 1979 pp. 105-115.
NFS: Network File System Protocol Specification, Internet Engineering Task Force RFC 1094, Mar. 1989, pp. 1-26.
Birrell et al., Implementing Remote Procedure Calls, ACM Transactions on Computer Systems, vol. 2, No. 1, Feb. 1984, pp. 39-59.
McKusick et al., Design of a General Purpose Memory Allocator for the 4.3BSD UNIX Kernel, Summer USENIX '88, San Francisco, Jun. 20-24, 1988, pp. 295-303.
Birrell et al., A Universal File Server, IEEE Transactions on Software Engineering, vol. SE-6, No. 5, Sep. 1980, pp. 450-454.
Carriero et al., The S/Net's Linda Kernel, ACM Transactions on Computer Systems, vol. 4, No. 2, May 1986, pp. 110-129.
Patterson et al., A Case for Redundant Arrays of Inexpensive Disks (RAID), Computer Science Division, Department of Electrical Engineering and Computer Science, University of California Berkeley, ACM, 1988, pp. 109-116.
Hornig, C., A Standard for the Transmission of IP Datagrams over Ethernet Networks, Internet Engineering Task Force RFC 894, Apr. 1984, 3 pages.
An American National Standard IEEE Standard for A Versatile Backplane Bus: VMEbus, The Institute of Electrical and Electronics Engineers, Inc., Mar. 28, 1988, pp. 1-320.
Postel, J., User Datagram Protocol, Internet Engineering Task Force RFC 768, Aug. 28, 1980, pp. 1-3.
Transmission Control Protocol DARPA Internet Program Protocol Specification, Internet Engineering Task Force RFC 793, Sep. 1981, pp. 1-88.
DOD Standard Transmission Control Protocol, Information Sciences Institute, University of Southern California, Jan. 1980, pp. 1-87.
Tan et al., SOS—Stan's Own Server A NFS file server for the IBM PC, Computer Science Research Department, Information & Computing Sciences Division, Lawrence Berkeley Laboratory, Aug. 1988, pp. 1-4.
Theimer et al., Preemptable Remote Execution Facilities for the V-System, Computer Science Department, Stanford University, ACM, 1985, pp. 2-12.
Berglund et al., Amaze: A Distributed Multi-Player Game Program using the Distributed V Kernel, The 4th International Conference on Distributed Computing Systems, May 14-18, 1984, San Francisco, IEEE Computer Society, pp. 248-297.
Nelson et al., An Overview of Functional Multiprocessing for NFS Network Servers, Auspex, Technical Report 1, Sixth Edition, Second Printing, Aug. 1992, pp. 1-27.
Stoller, S., Leader Election in Distributed Systems with Crash Failures, Indiana University CS Dept., 1997, pp. 1-15.
Sistine Inc., GFS Howto/Red Hat Global File System, 2001, 4 pages.
Siemens Inc., PRIMECLUSTER—Concepts Guide, Oct. 2001, pp. 1-80.
Microsoft Corp., Microsoft Windows NT clusters, White Paper, Nov. 1997.
Halpern et al., Knowledge and Common Knowledge in a Distributed Environment, IBM Research Journal 4421, 1986, pp. 1-46.
Garcia-Molina, H., Elections in a Distributed Computing System, IEEE Transactions on Computers, C-31(1): Jan. 1982, pp. 48-59.
Cheriton, D., Distributed Systems—CS244B Course Notes, vol. 1, Stanford University, Mar. 25, 1999.
Microsoft Windows NT Load Balancing Service- White Paper, 1999.
Cherkasova, L., FLEX: Load Balancing and Management Strategy for Scalable Web Hosting Service, Hewlett-Packard Labs, 6 pages.
Pai et al., Locality-Aware Request Distribution in Cluster-based Network Servers, ASPLOS VIII Oct. 1998, pp. 205-216.
Levy et al., Distributed File Systems: Concepts and ExamplesACM Computing Surveys, vol. 22, No. 4, Dec. 1990 54 pages.
Carson, K., Storage in the WAN, Ciprico Inc., Jul. 2001, pp. 1-4.
Karamanolis, et al., DiFFS: a Scalable Distributed File System, Hewlett-Packard Company, HPL-2001019, Jan. 24, 2001, 7 pages.
Muntz, D., Building a Single Distributed File System from Many NFS Servers, Hewlett-Packard Company, HPL-2001-176, Jul. 12, 2001, 5 pages.
Karamanolis et al., An Architecture for Scalable and Manageable File Services, Hewlett-Packard Company, HPL-2001-173, Jul. 12, 2001, pp. 1-14.
Zhang et al., Cross-Partition Protocols in a Distributed File Service, Hewlett-Packard Company, HPL-2001-129, May 23, 2001, pp. 1-21.
Mahalingam, et al., Data Migration in a Distributed File Service, Hewlett-Packard Company, HPL-2001-128, May 23, 2001, 12 pages.
Tannenbaum et al., Research Issues in Distributed Operating Systems, Department of Mathematics and Computer Science, Vrije Universiteit, The Netherlands, 10 pages.
Rieken et al., Adventures in . . . UNIX Kernel Structure and Flow, .sh consulting inc., California, Jun. 1990, 253 pages.
Howard et al., Scale and Performance in a Distributed File System, Carnegie Mellon University, ACM Transactions on Computer Systems, vol. 6, No. 1, Feb. 1988, pp. 51-81.
Lupper, A., Distributed File Systems, Department of Computer Science, University of Ulm, 1995, 25 pages.
Spanier, S., Comparing distributed file systems, Excelan Inc., Data Communications, Dec. 1987, pp. 173-186.
Kleiman, Vnodes: An Architecture for Multiple File System types in Sun Unix, Sun Microsystems, Usenix 1986 Summer Technical Conference & Exhibition, Georgia, Jun. 9-13, 1986, pp. 238-394.
Bechtolsheim et al., The SUN Workstation Architecture, Computer Systems Laboratory, Departments of Electrical Engineering and Computer Science, Stanford University, Technical Report No. 229, Jan. 15, 1982, 55 pages.
Welch, B., The File System Belongs in the Kernel, Xerox PARC, Usenix Association, Mach Symposium, pp. 233-247.
Bechtolsheim et al., The SUN Workstation Architecture, Computer Systems Laboratory, Departments of Electrical Engineering and Computer Science, Stanford University, Technical Report No. 229, Mar. 1982, pp. 1-15.
Schroder, W., PEACE: The distributed SUPRENUM operating system, Parallel Computing 7 (1988) North-Holland, pp. 325-333.
Kupfer, Michael, Sprite on Mach, University of California, Berkeley, Usenix Association, Mach III Symposium, pp. 307-322.
Roy, Paul, Unix File Access and Caching in a Multicomputer Environment, OSF Research Institute, Usenix Association, Mach III Symposium, pp. 21-37.
Panjwani, Mahmood, NFS on ISDN, UniForum 1988 Conference Proceedings, Dallas, TX, pp. 171-181.
Kelly, P., Functional Programming for Loosely-coupled Multiprocessors, The MIT Press, ISBN 0-273-08804-1,1989, pp. 1-4.
Sandberg, Russel, The Sun Network Filesystem: Design, Implementation and Experience, Sun Microsystems, Inc., pp. 1-16.
Solomon et al., The Roscoe Distributed Operating System, University of Wisconsin, ACM, May 1979, pp. 108-114.
Ennis, PC Network Services for Distributed System Design, IEEE Compcon Spring 1986, Mar. 1986, pp. 1-10.
Ousterhout et al., The Sprite Network Operating System, University of California Berkeley, IEEE, Feb. 1988, pp. 23-36.
Cardoza et al., Overview of Digital UNIX Cluster System Architecture, Digest of Papers of Compcon (Computer Society Conference) 1996 Technologies for The Information Superhighway, Feb. 25-28, 1996, Doc. No. XP010160905, pp. 254-259.
Kim et al., Volume Management in SAN Environment, Electronics and Telecommunications Research Institute, IEEE, Doc. No. XP010551728, Jun. 26, 2001, pp. 500-505.
Preslan et al., A 64-bit, Shared Disk File System for Linux, 16th IEEE Symposium on Mass Storage Systems, Mar. 15-18, 1999, pp. 22-41.
Thekkath et al., Frangipani: A Scalable Distributed File System, In Proceedings of the 16th ACM Symposium on Operating Systems Principles, Oct. 1997, 14 pages.
Tanenbaum et al., The Amoeba Distributed Operating System.
Sandberg et al., Design and Implementation of the Sun Network Filesystem, Summer '85 Usenix.
Douglis et al., A Comparison of Two Distributed Systems: Amoeba and Sprite.
Dibble et al., Bridge: A High-Performance File System for a Parallel Processors.
Cheriton, The Design of a Distributed Kernel, ACM '81, Nov. 9-11, 1981, pp. 46-52.
Cheriton, The V Kernel: A Software Base for Distributed Systems, IEEE Software, Apr. 1984, pp. 19-40.
Berglund, An Introduction to the V-System, IEEE Micro, Aug. 1986; pp. 35-52.
Way, Front-end processors smooth local network-computer integration, Electronics, Feb. 9, 1984, pp. 135-139.
Nelson et al., The Unix environment merges with a network-distributed system, Electronics, Feb. 9, 1984, pp. 131-134.
Owicki, Experience with the Firefly Multiprocessor Workstation, Digital Equipment Corp., Sep. 15, 1989.
Spector, Multiprocessing Architectures for Local Computer Networks, A Dissertation Submitted to the Dept. of Computer Science and the Com. On Graduate Studies of Stanford University in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy, Aug. 1981, 65 pages.
Giloi, SUPRENUM: A trendsetter in modern supercomputer development, Parallel Computing, Elsevier Science Publishers B. V. (North-Holland), 1987, 40 pages.
Dally et al., Architecture of a Message-Driven Processor, Association for Computing Machinery, Doc. No. ACM 0084-7495/87/0600-0189, 1987, 8 pages.
Barrera, A Fast Mach Network IPC Implementation, USENIX Association Mach Symposium, 11 pages.
Sunshine et al., Broad-Band Personal Computer LAN's, IEEE Journal on Selected Areas in Communications, vol. SAC-3, No. 3, May 1985, Doc. No. 0733-8716/85/0500-0408, 8 pages.
Schwartz et al., LFS—A Local File System for Multiprocessor NFS Network Servers, Auspex Systems Inc., Technical Report 4, Dec. 1989, Internet http://www.concentric.net/˜Ams/auspex/Tech4/Tech4.toc.html, Accessed Aug. 11, 2003, 16 pages.
Tanenbaum et al., AMOEBA System, Communications of the ACM, vol. 33, No. 12, Dec. 1990, 46-63, 18 pages.
Swinehart et al., WFS: A Simple Shared File System for a Distributed Environment, Association for Computing Machinery, Doc. No. ACM 0-89791-009-5/79/1200/0009, 1979, 9 pages.
Ramakrishnan et al., A Model of File Server Performance for a Heterogeneous Distributed System, Association for Computing Machinery, Doc. No. ACM 0-89791-201-2/86/0800-0338, 1986, 10 pages.
Solomon et al., Hardware Support for Interprocess Communication, Association for Computing Machinery, Doc. No. ACM 0084-7495/87/0600-0178$00.75, 1987, 11 pages.
Van de Goor et al., UNIX I/O In a Multiprocessor System, USENIX Winter Conference Feb. 9-12, 1988, 17 pages.
Thacker et al., Firefly: A Multiprocessor Workstation, Digital Systems Research Center, Dec. 30, 1987.
Powers, A Front-End TELNET/Rlogin Server Implementation, UniForum 1986 Conference Proceedings, p. 27-40.
Pawlowski et al., Network Computing in the UNIX and IBM Mainframe Environment, UniForum 1989, p. 287-302.
Hitz et al., Using Unix as One Component of a Lightweight Distributed Kernel for Multiprocessor File Servers, USENIX, Jan. 22-26, 1990.
Cheriton, The V Distributed System, Communications of the ACM, vol. 31, No. 3, Mar. 1988, pp. 314-333.
Cheriton, Local Networking and Internetworking in the V-System, ACM, 1983.
Ennis, Netbios: IBM's PC interface for distributed applications, Systems & Software, Dec. 1984.
Ennis, Upper Level Protocols for Broadband Local Networks, Mini/Micro West, Session 3/3, p. 1-5, Nov. 8-11, 1983.
Lien, Experience in Implementing XNS Protocols, Mini/Micro West, Session 3/2, p. 1-7, Nov. 8-11, 1983.
Gage, Real World Implementation of Upper Level Protocols, Mini/Micro West, Session 3/1, p. 1-5, Nov. 8-11, 1983.
Cheriton, An Experiment using Registers for Fast Message-Based Interprocessor Communication, p. 12-20.
Van Renesse et al., The Design of a High-Performance File Server, IEEE Transactions on Knowledge and Data Engineering, vol. 1, No. 2, pp. 22-27, Jun. 1989.
Traw et al., Hardware/Software Organization of a High Performance ATM Host Interface, IEEE Journal on Selected Areas in Communications (Special Issue on High Speed Computer/Network Interfaces), vol. 11, No. 2, pp. 240-253, 1993.
Tanenbaum, A., Computer Networks, Chapter 1, Section 1.7.2 pp. 35-36, Chapter 9, pp. 528-607, Second Edition, Prentice Hall, 1988.
Svobodava, L., File Servers for Network-Based Distributed Systems, Computing Surveys, vol. 16, No. 4, pp. 353-398, Dec. 1984.
Sullivan, T., Communications Network Management Enhancements for SNA Networks: An Overview, IBM Systems Journal, vol. 22, Nos. 1 2, 1983.
Stankovic, J., A Perspective on Distributed Computer Systems, IEEE Transactions on Computers, vol. c-33, No. 12, Dec. 1984.
SDLC (HDLC Normal Response Mode), JBM SDLC Protocol Tutorial, the Internet, www.jbmelectronics.com/products/sdls.htm, accessed Aug. 7, 2003.
Satyanarayanan, M., A Survey of Distributed File Systems, Dept. of Computer Science, Carnegie Mellon University, the Internet, citeseer.ist.psu.edu/ satyanarayanan89survey.html 1989.
Psounis, K., Active Networks: Applications, Security, Safety, and Architectures, IEEE Communications Surveys, First Quarter 1999, pp. 1-6, 1999.
Poor, V., The Concept of Attached Processing Resource Computer Systems, Symposium on Small Systems, Proceedings of the First SIGMINI Symposium on Small Systems, Chairman Paul A. V. Thomas, pp. 109-116, 1978.
Peters, M., What is High Performance Routing?(HPR), the Internet, International Business Machines website, www.3.ibm.com/software/network/tech-nology/appnhpr/hpr—wp.html, accessed Aug. 8, 2003.
Perkins, A., Larry Boucher Hangs Ten, Red Herring, the Internet, www.redherring.com/mag/issue03/—ten.html, Aug. 1993.
Padegs, A., System/360 and Beyond, IBM J. Res. Develop., vol. 25, No. 5, Sep. 1981.
Osadzinski, A., The Network File System, Computer Standards & Interfaces, 8, No. 1, pp. 45-48, 1988/1989.
O'Connell et al., JFS: A Secure Distributed File System for Network Computers, the Internet, citeseer.nj.nec.com/392625.html, 1999 and Trinity College Dublin Technical Reports, www.cs.tcd.ie/publications/tech-reports/.
Mullender et al., Protection and Resource Control in Distributed Operating Systems, Computer Networks, vol. 8, pp. 421-432, Oct. 1984.
Mullender et al., A Distributed File Service Based on Optimistic Concurrrency Control, Proceedings of the 10th ACM SIGOPS Conference, pp. 51-62, Association for Computing Machinery, Inc.,1985.
Mullender et al., The Design of a Capability-Based Distributed Operating System, The Computer Journal, vol. 29, No. 4, 1986.
Mullender et al., Amoeba A Distributed Operating System for the 1990s, Computer, IEEE, pp. 44-51, Jan. 1990.
Mukherjee et al., Making Network Interfaces Less Peripheral, IEEE Computer, vol. 31, No. 10, pp. 70-76, 1998.
Kshemkalyani et al., Scalability of Advanced Peer-to-Peer Networking (APPN)Networks, the Internet, International Business Machines website, www-3.ibm.com/soft-ware/network/technology/appnhpr/appn—acalability.html, Mar. 21, 1997.
Kanakia et al., The VMP Network Adapter Board (NAB): High-Performance Network Communication for Multiprocessors, Proc. ACM SIGCOMM 88, Aug. 1988.
Jarema et al., IBM Data Communications: A Quarter Century of Evolution and Progress, IBM J. Res. Develop., vol. 25, No. 5, Sep. 1981.
Introduction to SNA, Yale University, the Internet, www.yale.edu/pclt/COMM/SNA.HTM, Feb. 2, 1995.
Introduction to APPC, Yale University, the Internet, www.yale.edu/pclt/COMM/APPC.HTM, Feb. 8, 1995.
HDLC LAPB & NRM Level 2 Protocols, IBM HDLC Protocol Tutorial, the Internet, www.jbmelectronics.com/product/hdlc.htm,accessed Aug. 7, 2003.
Hariri, S., ECE 677X: High Performance Distributed Computing Systems, University of Arizona, www.ece.arizona.edu/˜hpdc,1999.
Hall et al., A Comparative Study of High Speed Networks, www.ieee-infocom.org/1998/papers/06c—3.pdf, 1998.
Farley, Marc, Building Storage Networks, Chapter 14 Accessing Data on S/390 MVS Mainframes from a SAN, Osborne/McGraw-Hill, 2000.
Druschel et al., Network Subsystem Design: A Case for an Integrated Path, IEEE Network, vol. 7, No. 4, IEEE, pp. 8-17, 1993.
Druschel et al., Experiences with a High-Speed Network Adaptor: A Software Perspective, “SIGCOMM”, pp. 2-13, 1994.
Drapeau et al., RAID-II: A High-Bandwidth Network File Server, “Proceedings of the 21st Annual International Symposium on Computer Architecture”, pp. 234-244, 1994.
Dittia et al., The APIC Approach to High Performance Network Interface Design: Protected DMA and Other Techniques, Washington University Technical Report WUCS-96-12, 1996.
Crocker, S., Initiating the ARPANET, Matrix News, 10(3), Mar. 2000.
Cooper et al., Protocol Implementation on the Nectar Communication Processor, {SIGCOMM} Symposium on Communications Architectures and Protocols, Philadelphia, PA, pp. 135-144, 1990.
Common Program Interface for Communications (CPI-C), the Internet; International Business Machines Website, www-3.ibm.com/software/network/technology/appnhpr/cpic.html; accessed Aug. 8, 2003.
Chow et al., Distributed Control of Computer Systems, IEEE Transactions on Computers, Vo. C-35, No. 6, pp. 564-567, Jun. 1986.
Chesson, G., Protocol Engine Design; Proc. 10th Summer 1987 USENIX Conference, pp. 209-215, Phoenix, AZ, Jun. 1987.
Chambers et al., Distributed Computing; Chapter 9, Sections 9.4.2-9.5.1, p. 144; Chapter 10, Sections 10.3.2-10.3.4, pp. 153-154; Chapter 11, p. 172 and 176-177; Chapter 13, Sections 13.1-13.4, pp. 193-199; Chapter 17, Section 17.1-17.4, pp. 239-250; Chapter 20, Sections 20.1-20.5, pp. 277-288; Academic Press, 1984.
Bashe et al. The Architecture of IBM's Early Computers; IBM J. Res. Develop., vol. 25, No. 5, pp. 363-375; Sep. 1981.
Auslander et al. The Evolution of the MVS Operating System; IBM J. Res. Develop.; vol. 25, No. 5, pp. 471-482; Sep. 1981.
ARPENET Information Brochure, the Internet, www.undergroundnews.com/files/texts/under-ground/hacking/arpa.htm, Dec. 1985.
Advanced Program-to-Program Communication (APPC), the Internet, International Business Machines website, www-3.ibm.com/software/network/ technology/appnhpr/appc.html.; accessed Aug. 8, 2003.
Advanced Peer-to-Peer Networking (APPN) and High Performance Routing (HPR), the Internet; International Business Machines Website, www-3.ibm.com/software/network/technology/appnhpr/; accessed Aug. 8, 2003.
November 1, 2022.
Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.
