J. S. Quarterman, A. Silberschatz, and J. L. Peterson, 4.2BSD and 4.3BSD as Examples of the UNIX System, ACM Computing Surveys, vol. 17(4), pp. 379-418, 1985.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....system, databases and middleware in such a way to make the security mechanisms as relatively independent and self contained components in the systems. Most of operating systems implement authorization logic in the security part of their kernels [9, 18, 19, 23, 25, 30, 31, 35, 42, 44, 45,48, 53, 54, 60, 64] There are also specialpurpose ad on security software packages that furnish authorization decisions for operating systems [9, 15, 16, 32] Abadi et al. 1] and Lampson et al. [39] developed a unified theory of authentication and access control in distributed systems. Practical ....

J. S. Quarterman, A. Silberschatz, and J. L. Peterson, 4.2BSD and 4.3BSD as Examples of the UNIX System, ACM Computing Surveys, vol. 17(4), pp. 379-418, 1985.

....patterns to dynamically regulate prefetching and caching, and show that application running time can be reduced by up to 42 . Seltzer et al. show in [48] by comparing the 4. 4BSD log structured file system (which is based on ideas first explored in Sprite LFS [42, 44] and the BSD fast file system [29, 41, 27], that the highest performing data organization is highly workload dependent. Temporary, memory based file systems [30, 35] have been added to many systems because conventional file creation deletion semantics are too heavy weight for some applications, costing more than a factor of two in ....

John S. Quarterman, Abraham Silberschatz, and James L. Peterson. 4.2BSD and 4.3BSD as examples of the UNIX system. Computing Surveys, 17(4):379--418, 1985.

....portable across any system that provides the same interface. Library operating systems themselves can be made portable by designing them to use a low level machine independent layer to hide hardware details. This technique has been widely used in the context of more traditional operating systems [74, 21]. As in traditional systems, an exokernel can provide backward compatibility in three ways: one, binary emulation of the operating system and its programs; two, implementing its hardware abstraction layer on top of an exokernel; and three, re implementing the operating system s abstractions on top ....

J.S. Quarterman, A. Silberschatz, and J.L. Peterson. 4.2BSD and 4.3BSD as examples of the UNIX system. Computing Surveys, 17(4):379--418, December 1985.

....formats for I O and mapping each device to the closest one. General purpose routines in the kernel then operate on each format. Unix, for example, has two major internal formats, which they call I O models : the block model for disk like devices and the character model for terminal like devices [26]. But common formats force compromise. There is a performance penalty paid when mismatches between the native device format and the internal format make translations 21 necessary. These translations can be expensive if the distance between the internal format and a particular device is large. ....

J.S. Quarterman, A. Silberschatz, and J.L. Peterson. 4.2BSD and 4.3BSD as Examples of the Unix System. ACM Computing Surveys, 17(4):379--418, December 1985.

....and other operating systems is in the combination of the synthetic machine interface and the kernel code synthesizer. No other operating system offers a high level interface and the potential to generate efficient code. Unix [13] has evolved into a large system with Fourth Berkeley Distribution [12] and AT T System V. Although the interface remains approximately the same in the many different variants of Unix, the synthetic machine interface is more orthogonal. To the best of our knowledge, no Unix system uses a kernel code synthesizer. The V kernel [7] and Amoeba [15] are two examples of ....

J.S. Quarterman, A. Silberschatz, and J.L. Peterson. 4.2BSD and 4.3BSD as examples of the Unix system. ACM Computing Surveys, 17(4):379--418, December 1985.

....directly accessible to user processes. No system calls or user to kernel copy operations are required to send and receive messages. As a result, host processes can communicate with lower latency (by a factor of 5) than would be possible using the UNIX socket interface of the host operating system [13]. Related work on host interfaces for high speed networks includes the VMP Network Adapter Board [10] and the Protocol Engine design [4] In these approaches, processing of specific transport protocols is offloaded to the network interface, but there is no provisionfor the execution of ....

....interface that was described in Section 3.5 provides applications with a flexible communication model. Since it uses the host CAB buffering and synchronization facilities directly, some or all of CAB memory must be mapped into applications address spaces. The familiar Berkeley socket interface [13] is also being implemented at this level. Initially, an emulation library will be provided for applications that can be re linked. Eventually, we will move this support into the UNIX kernel, which will intercept operations on Nectar connections and dispatch them to the CAB. This approach incurs ....

John S. Quarterman, Abraham Silberschatz, and James L. Peterson. 4.2BSD and 4.3BSD as examples of the UNIX system. ACM Computing Surveys, 17(4):379--418, December 1985.

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