H. Custer. Inside Windows/NT. Microsoft Press, Redmond, WA, 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of the CAL TSS [20] and Brinch Hansen s microkernel paper [13] are two classic rationales. Hydra was the most ambitious system to have the separation of kernel policy and mechanism as one of its central tenets [34] Modern revisitations of microkernels have also argued for kernel extensibility [16, 26, 1, 28, 30, 10]. Anderson [2] and Kiczales et al. 18] also recently argued for minimalism and customization. Two important differences between our work and previous approaches are that: 1) the fixed kernel interface in these systems is a high level one (e.g. page tables are implemented by the kernel) and (2) ....

H. Custer. Inside Windows/NT. Microsoft Press, Redmond, WA, 1993.

....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 ....

H. Custer. Inside Windows/NT. Microsoft Press, Redmond, WA, 1993.

....must be known statically. In a single address space model, the system rather than the applications coordinates the address bindings, to accommodate dynamic sharing patterns in a uniform way. Recent systems have taken steps in this direction; examples include based sections in Microsoft Windows NT [Custer 93] and the mmap facilities in recent Unix systems. Even in these systems, however, the mix of shared and private regions introduces several problems. Pointers may still be ambiguous: private data pointers in shared regions are difficult to detect or handle, and private code pointers (important for ....

....fully isolated software components and their data, interacting only through messages. This strict model of fully disjoint protection accommodates distribution, is tempting in its simplicity, and is central to both server structured [Young et al. 87, Rozier et al. 88, Mullender Tanenbaum 86, Custer 93] and object oriented [Allchin McKendry 83, Almes et al. 85] systems. However, we believe it is too simplistic and confining for several reasons: ffl Asymmetric trust relationships are common and can be exploited: A might accept inputs (or memory segments) from B even when B does not trust A. ....

Custer, H. Inside Windows/NT. Microsoft Press, 1993.

....problems associated with virtual caches. 2 Memory system requirements There is a core set of functional mechanisms associated with memory management that computer users have come to expect. These are found in nearly every modern microarchitecture and operating system (e.g. UNIX [3] Windows NT [15], OS 2 [16] 4.3 BSD [34] DEC Alpha [17, 46] MIPS [23, 32] PA RISC [25] PowerPC [29, 39] Pentium [31] and SPARC [52] and include the following: Address space protection. User level applications should not have unrestricted access to the data of other applications or the operating system. ....

H. Custer. "Inside Windows/NT." Tech. Rep., Microsoft Press, 1993.

....recently these benefits have not been important, because operating systems, file systems, and disk drivers have all been tightly coupled in monolithic kernels. However, with modern kernel designs in which an operating system supports multiple file systems (e.g. Mach [Golub 1990] and Windows NT [Custer 1993]) the benefits of separating file and disk management using LD are important. To demonstrate these benefits we built a prototype implementation of LD. This implementation, LLD, is logstructured and is based on the ideas used in Sprite LFS [Rosenblum and Ousterhout 1992] We combined LLD with ....

Custer, H., "Inside Windows/NT," Microsoft Press, Redmond, WA, 1993.

....of CAL TSS [27] and Brinch Hansen s microkernel paper [19] are two classic rationales. Hydra was the most ambitious system to have the separation of kernel policy and mechanism as one of its central tenets [48] Modern revisitations of microkernels have also argued for kernel extensibility [1, 15, 36, 39, 44]. The most important difference between our work and previous approaches is the explicit view that the kernel should not provide high level core abstractions. In other systems, the effective operating system interface is much higher level (e.g. page tables are implemented by the kernel) Current ....

H. Custer. Inside Windows/NT. Microsoft Press, Redmond, WA, 1993.

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