S. M. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, Feb. 1999.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....systems such as Microsoft Windows and standard distributions of open source systems such as Linux. Ballooning implicitly coaxes a guest OS into reclaiming memory using its own native page replacement algorithms. It has some similarity to the self paging technique used in the Nemesis system [11], which requires applications to handle their own virtual memory operations, including revocation. However, few applications are capable of making their own page replacement decisions, and applications must be modified to participate in 12 an explicit revocation protocol. In contrast, guest ....

Steven M. Hand. "Self-Paging in the Nemesis Operating System," Proc. Symposium on Operating Systems Design and Implementation, February 1999.

....architectures and implementations. If RBAC is to be adopted in practice, large scale engineering issues must be addressed. OASIS: an open architecture for secure, inter working services The OASIS project at the Computer Laboratory draws these threads together. An overview of OASIS is given in [2, 3], details of its architecture and engineering can be found in [4] and a formal model is presented in [5] OASIS is an access control system for open, interworking services in a distributed environment, with services being grouped into domains for the purpose of management. Services may be ....

....Paul Rovner, Roger Needham, Jerry Saltzer and Dave Clark. Ground rules I m not going to give formal semantics for the threads operations here. You can read the ones we wrote for Modula 2 [1] or you can read the reasonably good description in Chapter 17 of the Java Language Specification [3] (ignoring the stuff about re entrant mutexes) It s worth reading those specifications sometime, but the following summary should be enough for appreciating this paper. A condition variable, c, is associated with a specific lock, m. Calling c.Wait( enqueues the current thread on c ....

[Article contains additional citation context not shown here]

Hand, S., `Self-paging in the Nemesis operating system,' Proc. Usenix Third Symposium on Operating Systems Design and Implementation, February 1999.

....This makes it difficult to respond to changing load situations or suspected denial ofservice attacks because killing tasks is usually not an option. Finally, related work has shown that applications can benefit significantly from managing their memory resources according to their own policy [15, 19, 20]. This is possible because the application has specific knowledge and can therefore give far more accurate predictions on future resource usage than the kernel. Although this argument has mostly been used for ordinary memory resources, it can be applied to kernel memory as well. 1.2 Approach In ....

.... We consider this overly restrictive because this policy is always a compromise between performance and generality; related work has shown that applications are often ill served by the default operating system policy [1, 50] and can benefit significantly from managing their own memory resources [15, 19, 20, 27, 29, 39]. Also, while the allocation policy can be configured in some of the approaches, other policies, e.g. for placement or replacement, cannot be influenced at all. Furthermore, the effectivity of this approach depends strongly on the policy that is being used. FCFS, which is implemented in L4 and ....

Steven M. Hand. Self-paging in the Nemesis operating system. In Proceedings of the third symposium on Operating systems design and implementation, pages 73--86. USENIX Association, Feb 1999.

....ne its own revocation policies according to the needs of its higher level applications not only parallels the use of an application speci c page replacement policy, but is also another instantiation of the same overall idea. Memory management in the Nemesis operating system is a further example [Hand99] A frame allocator deals with the allocation and revocation of physical memory to and from applications. The approach is similar to the division of resources into guaranteed and best e ort that is provided in VServ using the revocation protocol. In Nemesis applications can be guaranteed a ....

Steven M. Hand. Self-Paging in the Nemesis Operating System. In Usenix Third Symposium on Operating Systems Design and Implementation (OSDI'99), February 1999. (p 123)

.... resources need to be multiplexed (e.g. for CPU scheduling and network output) such multiplexing is performed at the lowest possible level, in accordance with the principles put forward in [Tennenhouse89] Tasks such as protocol processing [Black97] thread scheduling and virtual memory paging [Hand99] are safely delegated to the applications themselves. Nemesis is discussed further in Chapter 4. 2.3.2 Resource Control in Mobile Code and Safe Languages Existing approaches to resource control in mobile code and safe languages have focused on two main areas: the negotiation for and allocation ....

....heap, to ensure that any roots to server heap objects that are stored in the calling 130 Activity Time (s) Cumulative Incremental Local function invocation 0.24 0.24 15.2 Runtime invocation 0.34 0.10 6.3 Heap manipulation 0.60 0.26 16.5 Chain manipulation 0.77 0. 17 10.8 Exception handling 0.90 0.13 8.2 Server callback 1.58 0.68 43.0 Total 1.58 1.58 100.0 Table 7.2: Breakdown of time spent in a service invocation thread s stack are correctly traced. Chain manipulation: Linking the calling thread into the list of callers for the service, for use in the event of server or client ....

[Article contains additional citation context not shown here]

Steven Hand. Self-Paging in the Nemesis Operating System. In OSDI

....on an extent level granularity by a trusted 32 user space filesystem driver. The usd driver maintains a cache of permission checks and makes call backs to the filesystem driver upon cache misses. Memory management Self paging is used by applications which require virtual memory [Hand98, Hand99] Separate interfaces are used for allocating (or potentially revoking) physical and virtual address space. The application is responsible for electing which physical frames should back which regions of its virtual address space and for paging data to disk where necessary. This design aids the ....

Steven M. Hand. Self-Paging in the Nemesis Operating System. In Proceedings of the 3rd Symposium on Operating Systems Design and Implementation (OSDI '99), pages 73--86. The USENIX Association, February 1999. (p 33) 182

....mechanisms and policies have been clearly demonstrated for many di erent classes of resource. Application speci c management of virtual memory has been extensively researched: Appel and Li [Appel91] provide general considerations for implementing application level VM primitives while Hand [Hand99] and Engler [Engler95] describe speci c implementations. User level network protocols are another area which has been covered by many groups: Cornell s U Net [vonEicken95] and the Virtual Interface Architecture [VIA97] derived from it, provide applications with a direct interface to the network ....

S. M. Hand; \Self-Paging in the Nemesis Operating System", 3rd USENIX Symposium on Operating Systems Design and Implementation (February 1999), pp.73-86. 13

....to provide quality of service to applications, in particular multimedia applications. It is a soft real time operating system. It is designed and implemented from scratch. In Nemesis, applications can reserve CPU time, transmit bandwidth on network interfaces, disk I O bandwidth [3] and memory [25]. In order to provide guarantees it is necessary that all resources used by or on behalf of an application are accounted for correctly. If you do not know who is using a resource you cannot provide the resource in a controlled way to the applications with the corresponding guarantees. In this ....

....client have an adverse e ect on the QoS observed by other clients [3] e.g. a video starts ickering when a compilation is started in the background. QoS crosstalk occurs when the operating system kernel or a shared server performs a signi cant amount of work on behalf of a number of applications [25]. As shown above, Nemesis avoids shared servers and applications perform as much work as possible 11 Priviledged: library shared shared shared library library code code code Appl. Appl. Appl. Driver Device Unpriviledged: Kernel Figure 1: The Nemesis structure. themselves using shared ....

[Article contains additional citation context not shown here]

S. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation (OSDI), New Orleans, USA, February 1999.

....such as Exokernel [12] which promotes the implementation of OS components as libraries under application control. Likewise, a SEDAbased OS should expose a virtual memory interface which makes physical memory availability explicit; this approach is similar to that of application controlled paging [7, 8]. 5. Related Work The SEDA design was derived from approaches to managing high concurrency and unpredictable load in a variety of systems. The Flash web server [21] and the Harvest web cache [4] are based on an asynchronous, event driven model which closely resembles the SEDA architecture. In ....

S. M. Hand. Self-paging in the Nemesis operating system. In Proceedings of OSDI '99, February 1999.

....does not infer the tag for a request in the absence of application support and does not exploit these for the scheduling of an application that picks up a tagged request. Precursors of this work are the Hierarchical Scheduler (HS) 9] with configurable CPU scheduling policies and the Nemesis OS [10]. Nemesis provides comprehensive inter application isolation for memory and file system. Both HS and Nemesis require applications to manage their own resource bindings. Workload Manager s (WLM s) 1] notion of a service class is similar to the notion of a VS. Since WLM manages requests separately ....

HAND, S. M. Self-Paging in the Nemesis Operating System. In Proceedings of the Third USENIX Symposium on Operating Systems Design and Implementation (New Oreleans, Lousiana, February 1999), USENIX, pp. 73-- 86.

....bypass the middleware s control mechanisms, e.g. by using their own service specific communication primitives or simply by binding communication libraries statically. Therefore, much attention has been focused on providing strong performance management mechanisms in the OS and network subsystem [4, 6, 7, 12, 15, 19, 20, 23, 25]. However, these solutions introduce more controls than necessary to manage QoS differentiation and defend the server from overload. We propose a novel combination of kernel level and middleware overload protection mechanisms called QGuard. QGuard learns the server s request handling capacity ....

....by sending replies over the same congested link. 5 Related Work A number of commercial and research projects address the problem of server overload containment and differential QoS. Ongoing research in this field can be grouped into three major categories: adaptive middleware [2, 3, 14] OS [4, 6, 12, 15, 17, 20, 23] and network centric solutions [7, 19] 5.1 Middleware for QoS Differentiation Middleware solutions coordinate graceful degradation across multiple resource sharing applications under overload. Since the middleware itself has only little control over the load of the system, they rely on ....

[Article contains additional citation context not shown here]

HAND, S. M. Self-Paging in the Nemesis Operating System. In Proceedings of the Third USENIX Symposium on Operating Systems Design and Implementation (New Oreleans, Lousiana, February 1999), USENIX, pp. 73--86.

....again serve as resource principals for operating systems. Like the other abstractions discussed above, they do not aim at providing di erentiated QoS in clusters, nor do they provide predictable QoS in application level metrics in server systems. 5.1. 8 Nemesis The Nemesis operating system [71, 57] follows a radically di erent approach for providing ne grained resource management. The application and most of the associated kernel processing is performed in the address space of the application. While this approach accurately accounts for all kernel processing to the corresponding ....

S. M. Hand. Self-Paging in the Nemesis Operating System. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, Feb. 1999.

....a small, 10 ms quantum, so such extensions have not been needed in our prototype. Petrou et al. also suggest an alternative approach to overcoming the lower limits that currencies impose. As discussed in Section 4.4, our scheme for managing memory is a temporary one. The Nemesis operating system [Han99] provides a more complete solution that also allows applications to obtain guaranteed memory shares. Nemesis ensures complete isolation by requiring that applications handle their own page faults. 7 Conclusions Our extended lottery scheduling resource management framework gives applications ....

Hand, S.M., "Self-Paging in the Nemesis Operating System," Proc. of the Third Symposium on Operating Systems Design and Implementation, February 1999.

.... 1: Memory Management Hierarchy incorporating Quality of Service A suitable vehicle for this work is Nemesis [22] a single address space operating system (SASOS) that supports QoS guarantees to applications and requires them to carry out their own virtual memory management known as self paging [11]. This combination of factors allows fine grained control over a domain s (analogous of a process or task) run time environment, making it ideal for experimentation with novel approaches to application centric memory management. The rest of this document is structured as follows: the overview of ....

....sender. What has been provided here is a necessarily superficial look at the Nemesis system. What it should do, however, is give enough of a background to help understand future sections. For a more detailed description, the reader is referred to [22] for a description of Nemesis and to [10] and [11] for a more detailed description of the VM management in particular. 3 Background Using a compressed cache involves splitting physical memory into two chunks: one chunk consists of the active pool of pages; the other is used as a cache where pages expelled from the active pool are compressed to ....

Hand, S. Self-Paging in the Nemesis Operating System. In Proceedings of 3rd Symposium on Operating Systems' Design and Implementation (New Orleans, February 1999).

....to provide their own implementation of any of the sub units. A suitable vehicle for this work is Nemesis [27] a single address space operating system (SASOS) that supports QoS guarantees to applications and requires them to carry out their own virtual memory management known as self paging [11]. This combination of factors allows ne grained control over a domain s (analogous of a process or task) run time environment, making it ideal for experimentation with novel approaches to application centric memory management. The rest of this document is structured as follows: the overview of ....

....sender. What has been provided here is a necessarily super cial look at the Nemesis system. What it should do, however, is give enough of a background to help understand future sections. For a more detailed description, the reader is referred to [27] for a description of Nemesis and to [10] and [11] for a more detailed description of the VM management in particular. 3 Background Remote paging involves using free memory on remote hosts to service page faults on behalf of local clients; there are two main avours: the rst involves a central server, or servers, with large (in the range of a ....

[Article contains additional citation context not shown here]

Hand, S. Self-Paging in the Nemesis Operating System. In Proceedings of 3rd Symposium on Operating Systems' Design and Implementation (New Orleans, February 1999).

....memory management hierarchy offering QoS to applications. A suitable vehicle for this work is Nemesis [23] a single address space operating system (SASOS) that supports QoS guarantees to applications and requires them to carry out their own virtual memory management (VMM) known as self paging [10]. This combination of factors allows quite fine grained control over a domain s 1 run time environment, making it ideal for experimentation with novel approaches to applicationcentric memory management. The purpose of the research described in this document is to provide a holistic approach to ....

....sender. What has been provided here is a necessarily superficial look at the Nemesis system. What it should do, however, is give enough of a background to help understand future sections. For a more detailed description, the reader is referred to [23] for a description of Nemesis and to [9] and [10] for a more detailed description of the VM management in particular. 3 Design and Implementation Figure 6 shows the design of the client side user level virtual memory management sub system. The focus of this is on the provision of a flexible user level virtual memory management unit that ....

Hand, S. Self-Paging in the Nemesis Operating System. In Proceedings of 3rd Symposium on Operating Systems' Design and Implementation (New Orleans, February 1999). 10

....the real time performance sensitiveness of multimedia applications, swapping should not be used in a multimedia OS [Steinmetz 95] Thus, we focus on pagingbased memory systems. Techniques such as demandpaging and memory mapped files have been successfully used in commodity OSs [Schulzrinne 96] Hand 99] However, these techniques fail to support multimedia applications, because they introduce unpredictable memory access times, cause poor resource utilization, and reduce performance. In the following subsections, we present new approaches for memory allocation and utilization, data replacement, ....

....amount of available buffers. Usually, data replacement is handled by the OS kernel where most applications use the same mechanism. Thus, the OS has full control, but the used mechanism is often tuned to best overall performance and does not support application specific requirements. In Nemesis [Hand 99] self paging has been introduced as a technique to provide QoS to multimedia applications. The basic idea of selfpaging is to require every application to deal with all its own memory faults using its own concrete resources . All paging operations are removed from the kernel where the kernel ....

Hand, S.M.: Self-Paging in the Nemesis Operating System, Proc. of 3 rd USENIX Symp. on Operating Systems Design and Implementation (OSDI'99), New Orleans, LA , USA, February 1999, pp. 73-86

No context found.

S. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd Symposium on Operating Systems Design and Implementation (OSDI 1999.

No context found.

S. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd Symposium on Operating Systems Design and Implementation (OSDI 1999.

....code on the same hardware) and in terms of resource consumption (so that clients may be charged according to their usage) W1.1 Core platform development. The core platform requirements of resource accounting and isolation fit closely with our experience developing the Nemesis operating system [12, 8]. Our basic platform design will follow a similar model: a low level hypervisor provides protection, scheduling and accounting. However, rather than running applications directly over this (as we did in Nemesis) we intend to host traditional OSs these form the unit of resource management, ....

HAND, S. M. Self-paging in the nemesis operating system. In Proceedings of the 3rd Symposium on Operating Systems Design and Implementation (OSDI '99) (Feb. 1999), The USENIX Association, pp. 73--86.

No context found.

S. M. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, Feb. 1999.

No context found.

Steven M. Hand. Self-paging in the Nemesis operating system. In Proc. 3rd OSDI, pages 73--86. USENIX Association, Feb 1999.

No context found.

HAND, S. Self-paging in the nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation (February 1999).

No context found.

Steven M. Hand. Self-Paging in the Nemesis Operating System. In Proceedings of the Third Symposium on Operatin Systems Design and Implementation, February 1999.

No context found.

Steven Hand. Self-paging in the nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, February 1999.

No context found.

S. Hand. Self-paging in the nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, February 1999.

No context found.

S. M. Hand. Self-Paging in the Nemesis Operating System. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, Feb. 1999.

No context found.

S. M. Hand. Self-paging in the Nemesis operating system. In Proceedings of the 3rd USENIX Symposium on Operating Systems Design and Implementation, pages 73--86, Feb. 1999.

No context found.

Steven M. Hand. Self-paging in the Nemesis operating system. In Proc. 3rd OSDI, pages 73-86. USENIX Association, Feb 1999.

No context found.

Steven M. Hand. Self-paging in the Nemesis operating system. In Proc. 3rd OSDI, pages 73--86. USENIX Association, Feb 1999.

No context found.

Steven Hand. Self-paging in the nemesis operating system. In Proc. of USENIX Symp. on Operating Systems Design and Implementation, February 1999.

No context found.

S. Hand. Self-paging in the Nemesis operating system. In USENIX Symposium on Operating Systems Design and Implementation, pages 73--86, New Orleans, LA, USA, February 1999.

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