D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, a distributed system. In Proceedings of the Spring 1991 EurOpen Conference, pages 43--50, May 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....interface it o ers, means that there is less need for something like a FiST translator to provide vnode like code translation for the HURD. Nevertheless, the HURD o ers an interface that is comparable to the vnode one and more. 6. 2 Plan 9 Plan 9 was developed at Bell Labs in the late 1980 s [Pike90, Pike91, Presotto93]. The Plan 9 approach to le system extension is similar to that of Unix. The Plan 9 mount system call provides a le descriptor that can be a user process or remote le server. After a successful mount, operations below the mount point are sent to the le server. Plan 9 s equivalent of the vnode ....

R. Pike, D. Presotto, K. Thompson, and H. Trickey. Plan 9, a distributed system. Proceedings of Spring EurOpen Conference, pages 43-50, May 1991.

....interesting to combine a knowledge based trace analysis tool [5] with active probing to accurately detect other abnormal TCP behavior. Finally, most of the TCP implementations probed in this paper are BSD derived TCP implementations. It is possible to probe non BSD derived TCPs (e.g. Plan9 TCP [13, 17] and Xinu TCP [3] to determine the similarities and differences. 6 Biographies Dr. Douglas Comer is a full professor of Computer Science at Purdue University. He has written numerous research papers and textbooks, and heads currently several networking research projects. He designed and ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, A Distributed System. In Proc. of the Spring

....objects which are charged to an account, including those a user may have lost track of. In most cases the user will want to remove such objects. This makes it important to be able to distinguish between lost and known objects. User level naming in Mungi is based on the Plan 9 naming service [Presotto et al. 1991], which allows users to tailor their own name spaces. There is no system wide human readable name for objects, lost objects in this context are those not appearing in a user s name space. In order to identify them the name service supports not only a mapping from human readable names to object ....

Presotto, D, Pike, R, Thompson, K, and Trickey, H (1991). Plan 9, a distributed system. In Spring EurOpen Conference, pages 43--50, Troms, Norway.

....system which converts human readable object names into object addresses. Mungi does not support a system wide naming facility other than virtual memory addresses; it is left to the user environment to supply a textbased object name space. We presently use an adaptation of the Plan 9 naming system [33], as its concept of user tailorable naming fits the Mungi model well. However, other views of the object space could be used, including the familiar UNIX naming hierarchy. One complication arises from to the fact that in the single address space one cannot guarantee that objects can grow to ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, a distributed system. In EurOpen Conference, pages 43--50, Troms, Norway, May 1991.

....machine. Limbo and Dis provide type safety and veri cation facilities similar to Java s. Inferno is oriented to network applications and provides data streaming and strong networking support. Inferno uses an extended le system namespace to provide applications with resources (similar to Plan 9 [35]) and uses namespace controls to restrict application access to those resources. Inferno does not support memory controls and does not appear to maintain a clear distinction between application and kernel. 6.2.2.4 NewtonOS NewtonOS [50] is an operating system that supports communication and ....

Presotto, D. L., Pike, R., Thompson, K., and Trickey, H. Plan 9, a distributed system. In Proceedings of the Spring 1991 EurOpen Conference (Troms, Norway, May 1991), EurOpen, pp. 43-50.

....that for certain replacement algorithms, the cache hit ratio may decrease as the cache size increases. Thus, in a FFS relying on FIFO, one would increase the cache sizes of the attached computer systems and, at the same time, obtain a worse performance in certain cases. The Plan 9 filesystem [10, 9] uses the FIFO rule to determine which of the possible cache map blocks is used when blocks are added to the cache. The authors of the current version of the Plan 9 filesystem assumed that the extra complexity and storage requirements to implement other algorithms such as LRU (see next section) ....

Presotto, D., Pike, R., Thompson, K., and Trickey, H. Plan 9, A Distributed System. In Proceedings of the Spring 1991 EurOpen Conference (May 1991).

....be interesting to combine a knowledge based trace analysis tool [5] with active probing to accurately detect other abnormal TCP behavior. Finally, most of the TCP implementations probed in this paper are BSD derived TCP implementations. It is possible to probe non BSD derived TCPs (e.g. Plan9 TCP [13, 17] and Xinu TCP [3] to determine the similarities and differences. 6 Biographies Dr. Douglas Comer is a full professor of Computer Science at Purdue University. He has written numerous research papers and textbooks, and heads currently several networking research projects. He designed and ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, A Distributed System. In Proc. of the Spring 1991 EurOpen Conf., pages 43--50, May 1991.

....some database functionalities such as cold backups. 3.2 System Database All data related to database support, such as log data and lock data, is stored as a database file, which we call the system database file. Uniformity of data access is thereby provided. The scheme is inspired by the Plan 9 [PPTT91] philosophy of treating all data uniformly as files. The system state is thus contained entirely in the database files in the system. As a result of storing system data in database files, user processes that run in the same shared memory as the Dal i system can access and share the data in the ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, a distributed system. In Proc. of the Spring 1991 EurOpen Conf., Troms, pages 43-- 50, May 1991.

....from standard pagers. Our true belief is that some optimization could be applied to Mach as well, despite performance penalties paid for user space implementation and compatibility issues. ffl Plan 9 is one of the few systems that treat TM as an inappropriate overhead and not promising add on [Pike90, Pres91]. Plan 9 is, like Sprite, completely different system to what we propose for our TM scheme. It is monolithical, with traditional UNIX like interface and does not support TM at all. The premise for rejecting TM is that tomorrow s hardware will be based on large, lightly loaded multiprocessors. Even ....

Presotto, D., Pike, R., Thompson, K., and Trickey, H. (May 1991) Plan 9, A Distributed System. Proceedings of the Spring EurOpen Conference, pages 43--50.

....bind command has been designed to make it easy to mount new file systems. In particular, file systems can be mounted before or after file systems already mounted at the same point. The before after concept replaces the notion of a search path. Plan 9 also supports the notion of a union mount [17]. The Plan 9 bind mechanism is a more elegant alternative to our double mounting plus comparison. However, a binding mechanism even an unusually flexible one such as that of Plan 9 addresses only part of the problem of switching between file systems. The harder part of the problem is ....

D. Presotto et al. Plan 9, A Distributed System. In Proc. Spring 1991 EurOpen Conf., pages 43--50, May 1991.

....testbed for studying protocol design issues in ATM networks. The testbed has been implemented on three platforms: a packet level network simulator [13] a network of Personal Computers (PCs) running the MS DOS operating system and interconnected by Ethernet, and a network of PCs running the Plan 9 [18, 19] operating system interconnected with Fore Systems ATM adaptors and FORE switches. Since the system was first developed on the simulator and then ported to the other systems, the software on all three platforms is nearly identical. Hence, we will discuss only the simulator version in this paper. ....

....708 9.2 AAL 243 3.2 Transport 1521 19.7 Session 995 12.9 Scheduler 387 5.0 Memory management 543 7.0 Link state routing 458 5.9 Signalling 2072 26.9 Multicast 784 10.2 Total 7711 100.0 Table 1: Number of lines in each layer of the protocol stack. A port of the stack to the Plan 9 operating system [18, 19] is substantially complete. This port contains the OS support functionality, but not yet the transport layer. With a null transport layer, we have achieved a user to user data rate of 65 Mbps between two 80486 PCs running the Plan 9 operating system and connected by Fore Systems HPA 200 cards and ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, A distributed system. In EurOpen, Proceedings of the Fall 1991 Conference, Tromso, Norway, May 1991.

....the file system is mounted, the user can use the logical file system in a network transparent way. Finally, there are other distributed file systems that, like Jade, provide mechanisms to let users construct their own name spaces. Examples include Tilde [Come86] QuickSilver [Cabr88] and Plan 9 [Pres91]. QuickSilver and Plan 9 do consider systems in large scale, but only in terms of size and wide area. Jade surpasses these systems in the ability to accommodate heterogeneity, allow for customization, and support interactions between name spaces. Generally, none of these three systems allows a ....

Presotto, D., Pike, R., Thompson, K., and Trickey, H. Plan 9, a distributed system. Technical report, AT&T Bell Laboratories, 1991.

....request and 100 byte String request operations include the time to marshal and unmarshal the request. The J Kernel uses object serialization to transmit a String while GVM and Alta use hand coded String marshal and unmarshal code. for multimedia applications. Eclipse [10] a descendant of Plan9 [38], introduced the concept of a reservation domain, which is a pool of guaranteed resources. Eclipse provides a guarantee of cumulative service, which means that processes execute at a predictable rate. It manages CPU, disk, and physical memory. Our work is orthogonal, because we are examining the ....

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, a distributed system. In Proc. of the USENIX Workshop on Microkernels and Other Kernel Architectures, 1992.

....type to a Unix system. The new filesystem is fully described by the implementation of its interface functions. These functions are then compiled into the kernel and added to a dispatch table. 2.2. 2 Unified Resource Interface ffl Plan 9, an operating system developed at Bell Laboratories ([PRES90]) offers a unified resource interface through the filesystem namespace, and the ability to extend the system by attaching a server process to the namespace. 2.2.3 Application Control of Policy Two policy decisions are critical to the performance of an I O intensive application: what data is ....

....[SELT93] provide the same interface to application programs, but the underlying representations are very different. Network sockets and disk files are both accessed through the use of file descriptors, although they are supported by entirely different implementations. Some systems (e.g. Plan 9 [PRES90]) choose a single, compromise interface for all resources. The disadvantage of choosing one abstraction for all resources is that each must implement the complete interface, and none can extend it. VINO provides a more general, hierarchical resource model that allows behavior to be shared or ....

Presotto, D., R. Pike, H. Trickey, and K. Thompson, "Plan 9, a Distributed System, Proceedings of the Spring 1991 EurOpen Conference (May 1991).

....interface of type Context provides a flat name space in which textual strings can be bound to objects of arbitrary types. Naming graphs can be built by binding names in one Context to other Contexts. Name spaces can also be composed in an ordered way in the manner of Plan 9 s union directories [7]. Interfaces conforming to type Context are used extensively within Nemesis. Nemesis also provides a module called TypeSystem. This component of the system encapsulates data structures representing every interface type known to the system together with all operation signatures and concrete types ....

Presotto, D., Pike, R., Thompson, K., and Trickey, H. Plan 9, a Distributed System. In Proceedings of the Spring 1991 EurOpen Conference, Tromsoe (May 1991), pp. 43--50.

....non volatile RAM streams into a log on a disk or RAID and from there to a log in WORM storage. Caching and backup will all be integrated in one simple mechanism. An extra advantage is that the backup system is on line and that historic data is available in the regular name space, much like Plan 9 [Presotto et al. 1991]. 5 Processing Multimedia The performance of modern computing devices and networks allows the consideration of applications which integrate various real time media, such as video and audio, into a distributed computing system. Applications can be identified which need to manipulate the media data ....

Presotto et al. [1991] D. Presotto, R. Pike, K. Thompson and H. Trickey, Plan 9, A Distributed System, Proceedings of the Spring 1991 EurOpen Conference, Tromsų, Norway, May 1991, 43-- 50.

No context found.

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, a distributed system. In Proceedings of the Spring 1991 EurOpen Conference, pages 43--50, May 1991.

No context found.

D. Presotto, R. Pike, K. Thompson, and H. Trickey. Plan 9, A Distributed System. In Proceedings of the Spring 1991 EurOpen Conf., pages 43--50, May 1991.

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