DOCSLIB.ORG

Automatic Recovery from Resource Exhaustion Exceptions by Collecting Leaked Resources∗

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Automatic Recovery from Resource Exhaustion Exceptions by Collecting Leaked Resources∗ Dai et al. / J Zhejiang Univ-Sci C (Comput & Electron) 1 Journal of Zhejiang University-SCIENCE C (Computers & Electronics) ISSN 1869-1951 (Print); ISSN 1869-196X (Online) www.zju.edu.cn/jzus; www.springerlink.com E-mail: [email protected] Automatic Recovery from Resource Exhaustion Exceptions by Collecting Leaked Resources∗ Zi-ying DAIy1, Xiao-guang MAOyz1,2, Li-qian CHEN1, Yan LEI1,3 1College of Computer, National University of Defense Technology, Changsha 410073, China 2Laboratory of Science and Technology on Integrated Logistics Support, National University of Defense Technology, Changsha 410073, China 3Department of Computer Science, University of California, Davis, USA yE-mail: [email protected]; [email protected] Received Nov. X, 2013; Revision accepted XX, 2013; Crosschecked XX, 2013 Abstract: Despite the availability of garbage collectors, programmers must manually manage non-memory finite system resources such as file descriptors. Resource leaks can gradually consume all available resources and cause programs to raise resource exhaustion exceptions. However, programmers commonly provide no effective recovery for resource exhaustion exceptions, which often can cause programs to halt without completing their tasks. In this paper, we propose to automatically recover programs from resource exhaustion exceptions caused by resource leaks. We transform programs so that they can catch resource exhaustion exceptions, collect leaked resources, and then retry failed code. A resource collector is designed to identify leaked resources and safely release them. We implement our approach for Java programs. Experimental results show that our approach can successfully handle resource exhaustion exceptions caused by reported resource leaks and allow programs to continue to complete their tasks with an average execution time increase of 2.52% and negligible byte-code size increases. Key words: Failure avoidance, Resource leaks, Resource collection, Exception handling, Reliability doi:XX/jzus.C1000000 Document code: A CLC number: 1 Introduction bug that occurs when the cleanup method of the re- source is not invoked after its last use. Resource leaks Automatic garbage collection has gained con- are common in Java programs (Torlak and Chandra, siderable success in many mainstream programming 2010). Growing resource leaks can degrade an appli- languages, such as Java and C#. A garbage col- cation’s performance and can even result in system lector relieves programmers from manual memory crashes due to resource exhaustion. management and improves productivity and pro- gram reliability (Dybvig et al., 1993). However, The large majority of modern programs rely on there are many other non-memory finite system re- exception handling constructs to notify abnormal sit- sources (e.g. file descriptors and database connec- uations and allow customized recoveries from excep- tions) that programmers must manage manually. For tions. When a semantic error occurs or some ex- programs written in Java-like languages, once ac- ceptional situation is encountered, an exception is quired, a resource must be released by explicitly call- thrown (e.g. throw in Java). This exception causes ing a cleanup method. A resource leak is a software the control flow to transfer from where the excep- tion occurs to a point where the exception is caught z Corresponding author * Projects (Nos. 61379054 and 91318301) supported by the (e.g. try and catch in Java). If an exception is not National Natural Science Foundation of China, and Projects caught within the method where it occurs, it is im- (No. 2012AA011201) supported by National High Technology Research and Development Program of China (863 program) plicitly propagated to the caller of this method. If all ⃝c Zhejiang University and Springer-Verlag Berlin Heidelberg 2013 available resources are consumed (or leaked), a fur- 2 Dai et al. / J Zhejiang Univ-Sci C (Comput & Electron) ther request for such resources will typically cause This paper presents an approach to automat- the program to throw a resource exhaustion excep- ically recover from REEs caused by resource leak- tion (REE). For example, a Java program will throw s by collecting leaked resources and make the pro- a FileNotFoundException saying “Too many open gram execution able to proceed to complete its task. files" when no more available file descriptors can be Our approach has two key components. The first used to open a file. component is the program transformer that analyzes Programmers can catch exceptions and provide the program, finds method calls where REEs can be their recovery code. However, the recovery code pro- thrown and transforms the program by adding recov- vided by the the programmer is often unsatisfacto- ery code for REEs. The recovery strategy consists of ry. The Java code in Fig. 1a is such an example. collecting leaked resources first and then retrying the This code snippet is from an old version of Ant1 exception-throwing method calls. We require that and is the running example used throughout this pa- the REE-throwing method is failure atomic (Fetzer per. The programmer opens a pattern file in line et al., 2004) (i.e., the method leaves the program in 5 but forgets to close it. If this method is repeat- a consistent state before exceptions are propagated edly called in cases where there are many pattern to its caller). For example, the transformed result files for a task, the available file descriptors can be for the exception-throwing code in the lines 2 and exhausted. The file open (line 3) can fail with a 3 in Fig. 1a is presented in Fig. 1b2. The sec- thrown FileNotFoundException that is caught (line ond component is the resource collector (called by 6). The recovery code for this exception provided by System.rc() in the line 6 in Fig. 1b) that collects the programmer is disappointing because the pro- leaked resources. First, the resource collector identi- grammer just logs this exception, re-throws anoth- fies leaked resources as the unreleased and unreach- er exception and terminates the execution of this able resources. For garbage collected languages, we method (line 9), without any recoveries. The fur- adapt the garbage collector to retain leaked resources ther the exception propagates from this method, the during garbage collections. Second, corresponding less likely the program can be successfully recovered cleanup methods such as close of BufferedReader from it. This usually causes the entire program to for the code in Fig. 1a are invoked to safely release halt without completing the task. Instead of an ex- these leaked resources in the right order. We ensure ceptional case, this logging-rethrowing-terminating the safety of the resource collector by guaranteeing strategy is common for exception handling accord- that when a resource is released there are no objects ing to recent studies (Shah et al., 2010; Cabral and that depend on it and that have some actions (e.g., Marques, 2007). close and finalize) to perform in the future, and Designing effective recovery strategies for excep- this resource does not refer to resources that may be tions (i.e. recovering from exceptional states and manipulated later by the program. continuing the execution of the program to complete We implement our approach based on Soot its task) is difficult. When encountering a resource (Vallée-Rai et al., 1999) and Jikes RVM (Arnold exhaustion exception, programmers typically do not et al., 2000) for Java programs. The input to our know where to find available resources. Existing ex- approach is REEs as well as their corresponding ception recovery approaches (Carzaniga et al., 2013; resource specifications. We conduct a series of ex- Chang et al., 2009) cannot avoid failures manifested periments to evaluate the effectiveness and overhead as REEs. Even if they can fix the causal resource of our approach on standard benchmarks in litera- leak, there is no available resources to complete the ture and reported resource leaks from real-world pro- task without collecting leaked resources. Consider- grams. The experimental results show that our ap- ing the abundance of resource leaks and the poor proach can successfully recover from REEs caused by quality of exceptional handling, REEs pose a great 2Our approach actually transforms the method threat to the reliability of programs. FileInputStream(File) that is called by FileReader(File). We only transform calls to source methods of REEs. See 1In current version of Ant, the opened file is closed within Section 2 for details. The transformation in Fig. 1b is for a finally statement at the end of this method. Howev- illustration. All classes in this paper are from the Java sys- er, the handling code for the IOException (superclass of tem library unless explicitly stated otherwise. We omit the FileNotFoundException) remains. package name for brevity without confusions. Dai et al. / J Zhejiang Univ-Sci C (Comput & Electron) 3 1 private void readPatterns(File patternfile, …) throws BuildException { 1 FileReader reader = null ; 2 try { BufferedReader patternReader = 2 try { 3 new BufferedReader( new FileReader(patternfile)); 3 reader = new FileReader(patternfile); 4 // Create one NameEntry in the pattern list for each line in the file. 4 } catch (FileNotFoundException e) { 5 … 5 if (e.getMessage().contains("Too many open files")) { 6 } catch (IOException ioe) { 6 System.rc(e); // collect leaked files 7 String msg = "An error occurred while reading from pattern file: " 7 reader = new FileReader(patternfile); 8 + patternfile; 8 } else 9 throw new BuildException(msg, ioe); 9 throw e; 10 } 10 } 11 } 11 BufferedReader patternReader = new BufferedReader (reader ); (a) (b) Fig. 1 The left part (a) is an example code snippet from Ant, and the right part (b) is the transformed result for the lines 2 and 3 from the left part these reported resource leaks and make the programs Resource Specification Resource able to continue to complete their tasks. The run- Collection time overhead for benchmark programs is very low, REE around 3%, and the average execution time increase Hardened is 2.56%.
Load more

Recommended publications
  • Operating Systems (Undergrad): Spring 2020 Midterm Exam
    New York University CSCI-UA.202: Operating Systems (Undergrad): Spring 2020 Midterm Exam • This exam is 75 minutes. • The answer sheet is available here: – Section 001 (Aurojit Panda) – Section 003 (Michael Walfish) The answer sheet has the hand-in instructions and the video upload instructions. • There are 14 problems in this booklet. Many can be answered quickly. Some may be harder than others, and some earn more points than others. You may want to skim all questions before starting. • This exam is closed book and notes. You may not use electronics: phones, tablets, calculators, laptops, etc. You may refer to ONE two-sided 8.5x11” sheet with 10 point or larger Times New Roman font, 1 inch or larger margins, and a maximum of 55 lines per side. • Do not waste time on arithmetic. Write answers in powers of 2 if necessary. • If you find a question unclear or ambiguous, be sure to write any assumptions you make. • Follow the instructions: if they ask you to justify something, explain your reasoning and any important assumptions. Write brief, precise answers. Rambling brain dumps will not work and will waste time. Think before you start writing so that you can answer crisply. Be neat. If we can’t understand your answer, we can’t give you credit! • If the questions impose a sentence limit, we will not read past that limit. In addition, a response that includes the correct answer, along with irrelevant or incorrect content, will lose points. • Don’t linger. If you know the answer, give it, and move on.
    [Show full text]
  • Automatic Collection of Leaked Resources
    IEICE TRANS. INF. & SYST., VOL.E96–D, NO.1 JANUARY 2013 28 PAPER Resco: Automatic Collection of Leaked Resources Ziying DAI†a), Student Member, Xiaoguang MAO†b), Nonmember, Yan LEI†, Student Member, Xiaomin WAN†, and Kerong BEN††, Nonmembers SUMMARY A garbage collector relieves programmers from manual rent approaches either strive to detect and fix these leaks memory management and improves productivity and program reliability. or provide new language features to simplify resource man- However, there are many other finite system resources that programmers agement [2], [3], [5]–[8]. Although these approaches can must manage by themselves, such as sockets and database connections. Growing resource leaks can lead to performance degradation and even achieve success to some extent, there are some escaped re- program crashes. This paper presents the automatic resource collection source leaks that manifest themselves after programs have approach called Resco (RESource COllector) to tolerate non-memory re- been deployed. We also note that similar to memory leaks, source leaks. Resco prevents performance degradation and crashes due to leaks of other resources are not necessarily a problem. A resource leaks by two steps. First, it utilizes monitors to count resource ff consumption and request resource collections independently of memory few or a small amount of leaked resources will neither a ect usage when resource limits are about to be violated. Second, it responds program behavior nor performance. Only when accumu- to a resource collection request by safely releasing leaked resources. We lated leaks exhaust all available resources or lead to large ex- implement Resco based on a Java Virtual Machine for Java programs.
    [Show full text]
  • State-Taint Analysis for Detecting Resource Bugs
    JID:SCICO AID:2114 /FLA [m3G; v1.218; Prn:10/07/2017; 11:30] P.1(1-17) Science of Computer Programming ••• (••••) •••–••• Contents lists available at ScienceDirect Science of Computer Programming www.elsevier.com/locate/scico State-taint analysis for detecting resource bugs ∗ Zhiwu Xu a, Cheng Wen a, Shengchao Qin b,a, a College of Computer Science and Software Engineering, Shenzhen University, China b School of Computing, Teesside University, UK a r t i c l e i n f o a b s t r a c t Article history: To ensure that a program uses its resources in an appropriate manner is vital for program Received 3 January 2017 correctness. A number of solutions have been proposed to check that programs meet such Received in revised form 20 June 2017 a property on resource usage. But many of them are sophisticated to use for resource Accepted 25 June 2017 bug detection in practice and do not take into account the expectation that a resource Available online xxxx should be used once it is opened or required. This open-but-not-used problem can cause Keywords: resource starvation in some cases, for example, smartphones or other mobile devices where Resource bug resources are not only scarce but also energy-hungry, hence inappropriate resource usage Static analysis can not only cause the system to run out of resources but also lead to much shorter battery Energy leak life between battery recharge. That is the so-call energy leak problem. Android In this paper, we propose a static analysis called state-taint analysis to detect resource bugs.
    [Show full text]
  • Debug Your Threading and Memory Errors
    Kevin O’Leary Intel SPDK, PMDK, Intel® Performance Analyzers Virtual Forum 01 Intel Inspector overview 02 Intel Inspector features 03 Summary SPDK, PMDK, Intel® Performance Analyzers Virtual Forum 2 Intel® Trace Analyzer Cluster N Scalable Tune MPI & Collector (ITAC) ? Intel APS Intel MPI Tuner Y Memory Effective Y Bandwidth N threading Vectorize Sensitive ? Intel® Inspector ? N Find any Y correctness errors Optimize Thread in your threads and bandwidth memory! Intel® Intel® Intel® VTune™ Profiler Advisor VTune™ Profiler SPDK, PMDK, Intel® Performance Analyzers Virtual Forum 3 Size and complexity of Correctness tools find defects applications is growing during development prior to shipment Reworking defects is 40%-50% Reduce time, effort, and of total project effort cost to repair Find errors earlier when they are less expensive to fix SPDK, PMDK, Intel® Performance Analyzers Virtual Forum 4 Debugger Breakpoints Correctness Tools Increase ROI By 12%-21%1 ▪ Errors found earlier are less expensive to fix ▪ Several studies, ROI% varies, but earlier is cheaper Diagnosing Some Errors Can Take Months ▪ Races & deadlocks not easily reproduced ▪ Memory errors can be hard to find without a tool Intel® Inspector dramatically sped up Debugger Integration Speeds Diagnosis our ability to track down difficult to isolate threading errors before our ▪ Breakpoint set just before the problem packages are released to the field. ▪ Examine variables & threads with the debugger Peter von Kaenel, Director, Diagnose in hours instead of months Software Development,
    [Show full text]
  • Unit-Iv Process,Signals and File Locking
    UNIT-IV PROCESS, SIGNALS AND FILE LOCKING III-I R14 - 14BT50502 PROCESS: When you execute a program on your UNIX system, the system creates a special environment for that program. This environment contains everything needed for the system to run the program as if no other program were running on the system. Whenever you issue a command in UNIX, it creates, or starts, a new process. When you tried out the ls command to list directory contents, you started a process. A process, in simple terms, is an instance of a running program. When you start a process (run a command), there are two ways you can run it − Foreground Processes Background Processes FOREGROUND PROCESSES: By default, every process that you start runs in the foreground. It gets its input from the keyboard and sends its output to the screen. Example: $ls ch*.doc When a program is running in foreground and taking much time, we cannot run any other commands (start any other processes) because prompt would not be available until program finishes its processing and comes out. BACKGROUND PROCESSES: A background process runs without being connected to your keyboard. If the background process requires any keyboard input, it waits. The advantage of running a process in the background is that you can run other commands; you do not have to wait until it completes to start another! The simplest way to start a background process is to add an ampersand (&) at the end of the command. Example: $ls ch*.doc & PROCESS IDENTIFIERS: The process identifier – normally referred to as the process ID or just PID, is a number used by most operating system kernels such as that of UNIX, Mac OS X or Microsoft Windows — to uniquely identify an active process.
    [Show full text]
  • State-Taint Analysis for Detecting Resource Bugs
    State-Taint Analysis for Detecting Resource Bugs Zhiwu Xu1 Dongxiao Fan1 Shengchao Qin2,1 1 College of Computer Science and Software Engineering, Shenzhen University, China 2 School of Computing, Teesside University, UK Email: [email protected], [email protected], [email protected] Abstract—To verify whether a program uses resources in it unused/unattended, in other cases this may lead to a valid manner is vital for program correctness. A number of more severe problems. For instance, when some resource solutions have been proposed to ensure such a property for is very limited and is not released timely, this issue can resource usage. But most of them are sophisticated to use for resource bugs detection in practice and do not concern about lead to a major problem, causing resource starvation the issue that an opened resource should be used. This open- and severe system slowdown or instability. Specifically, but-not-used problem can cause resource starvation in some for mobile devices, such as tablets and smartphones, case as well. In particular, resources of smartphones are not which have become hugely popular, the resource is only scarce but also energy-hungry. The misuse of resources rather limited, specially power energy (i.e. the battery could not only cause the system to run out of resources but also lead to a shorter battery life. That is the so-call energy capacity). Most resources of mobile devices are not only leak problem. scarce but also energy-hungry, such as GPS, WiFi, camera, Aiming to provide a lightweight method and to detect and so on.
    [Show full text]
  • Processes, Address Spaces, and Context Switches
    Processes, Address Spaces, and Context Switches Chester Rebeiro IIT Madras Executing Apps (Process) • Process – A program in execution – Most important abstraction in an OS – Comprises of $gcc hello.c • Code from ELF In the • Data user space • Stack of process ELF • Heap Executable Process • State in the OS In the kernel (a.out) $./a.out • Kernel stack space – State contains : registers, list of open files, related processes, etc. 2 Program ≠ Process Program Process code + static and global data Dynamic instantiation of code + data + heap + stack + process state One program can create several A process is unique isolated entity processes 3 Process Address Space • Virtual Address Map MAX_SIZE – All memory a process can Stack address – Large contiguous array of addresses from 0 to Heap MAX_SIZE Data Text (instructions) 0 4 Process Address Space • Each process has a different address space • This is achieved by the use of virtual memory • Ie. 0 to MAX_SIZE are virtual memory addresses MAX_SIZE Stack Stack MAX_SIZE Heap Heap Data Data Process A Process B Process A Text Text Process B Page Table (instructions) (instructions) Page Table 0 0 5 Virtual Address Mapping Process A Process B Stack Stack Heap Heap Process A Process B Data Page Page Data Table Table Text Text (instructions) (instructions) Virtual Memory Physical Memory Virtual Memory 6 Advantages of Virtual Address Map • Isolation (private address space) – One process cannot access another process’ memory • Relocatable – Data and code within the process is relocatable • Size – Processes can be much larger than physical memory 7 Kernel can access User Process can access Address Map in xv6 Process DeviceMemory (instructions) Text + Data, Text Kernel Stack Heap Data Text (0x80000000) KERNBASE 0xFE000000 0 • every process address space address process every mapped kernel into Entire – – kernelspace Easyaccess userof datafrom duringsystem calls) usercode kernelto code(ie.
    [Show full text]
  • Lecture 3 : Process Management
    Lecture 3 : Process Management INSTRUCTOR : DR. BIBHAS GHOSHAL ([email protected]) 1 Lecture Outline What is Process? Process States Process Creation Process Address Space Creating a process by Cloning Process Termination Zombie Process Orphans Process Process Address Map in xv6 2 Process Program in Execution Process Comprises of: #include<stdio.h> . Code int main(){ . Data In User space of process Char str[] = “Hello World!\n”; . Stack Printf(“%s”,str); . Heap } . State in OS . $ gcc hello.c Kernel stack In Kernel space of process ELF Process Executable(a.out) $ ./a.out Program Process . Code + static & global data . Dynamic instantiation of code + data + heap + stack + process . One program can create several state processes . A process is unique isolated entity 3 Data Structure of Process Stack Recursive calls Attributes of a Process . Process Id Heap Dynamic allocation of data structures . Program counter . Static Variable Process State . & Once created, it will be there for lifetime Priority . Global Variable General Purpose Register . List of open files Executable a.out . List of open devices . Protection While executing a process, you are restricted to process boundary or else segmentation fault will occur. Heap grows upwards while Stack grows downwards. 4 Process State Process Scheduled Exit NEW READY RUN Terminate ◦ Created I/O Request over I/O Request WAIT Running: In the running state, a process is running on a processor. This means it is executing instructions. Ready: In the ready state, a process is ready to run but for some reason the OS has chosen not to run it at this given moment. Wait: In the blocked state, a process has performed some kind of operation that makes it not ready to run until some other event takes place.
    [Show full text]
  • Lightweight and Modular Resource Leak Verification
    Lightweight and Modular Resource Leak Verification Martin Kellogg∗ Narges Shadab∗ Manu Sridharan Michael D. Ernst University of Washington, University of California, University of California, University of Washington, Seattle, USA Riverside, USA Riverside, USA Seattle, USA [email protected] [email protected] [email protected] [email protected] ABSTRACT 1 INTRODUCTION A resource leak occurs when a program allocates a resource, such as A resource leak occurs when some finite resource managed by the a socket or file handle, but fails to deallocate it. Resource leaks cause programmer is not explicitly disposed of. In an unmanaged lan- resource starvation, slowdowns, and crashes. Previous techniques to guage like C, that explicit resource might be memory; in a managed prevent resource leaks are either unsound, imprecise, inapplicable language like Java, it might be a file descriptor, a socket, or a data- to existing code, slow, or a combination of these. base connection. Resource leaks continue to cause severe failures, Static detection of resource leaks requires checking that de- even in modern, heavily-used Java applications [15]. This state- allocation methods are always invoked on relevant objects before of-the-practice does not differ much from two decades ago [35]. they become unreachable. Our key insight is that leak detection can Microsoft engineers consider resource leaks to be one of the most be reduced to an accumulation problem, a class of typestate prob- significant development challenges22 [ ]. Preventing resource leaks lems amenable to sound and modular checking without the need remains an urgent, difficult, open problem. for a heavyweight, whole-program alias analysis.
    [Show full text]
  • Downloaded from Some Repair a Leak) That Consistently Produces Correct and Safe Chat Room
    JOURNAL OF LATEX CLASS FILES, VOL. 14, NO. 8, AUGUST 2015 1 Automated Repair of Resource Leaks in Android Applications Bhargav Nagaraja Bhatt and Carlo A. Furia Abstract—Resource leaks—a program does not release resources it previously acquired—are a common kind of bug in Android applications. Even with the help of existing techniques to automatically detect leaks, writing a leak-free program remains tricky. One of the reasons is Android’s event-driven programming model, which complicates the understanding of an application’s overall control flow. In this paper, we present PLUMBDROID: a technique to automatically detect and fix resource leaks in Android applications. PLUMBDROID builds a succinct abstraction of an app’s control flow, and uses it to find execution traces that may leak a resource. The information built during detection also enables automatically building a fix—consisting of release operations performed at appropriate locations—that removes the leak and does not otherwise affect the application’s usage of the resource. An empirical evaluation on resource leaks from the DROIDLEAKS curated collection demonstrates that PLUMBDROID’s approach is scalable, precise, and produces correct fixes for a variety of resource leak bugs: PLUMBDROID automatically found and repaired 50 leaks that affect 9 widely used resources of the Android system, including all those collected by DROIDLEAKS for those resources; on average, it took just 2 minutes to detect and repair a leak. PLUMBDROID also compares favorably to Relda2/RelFix—the only other fully automated approach to repair Android resource leaks—since it usually detects more leaks with higher precision and producing smaller fixes.
    [Show full text]
  • Executing Apps (Process)
    Processes Chester Rebeiro IIT Madras Executing Apps (Process) • Process – A program in execution – Most important abstraction in an OS – Comprises of $gcc hello.c • Code • Data from ELF In the user space • Stack of process ELF • Heap Executable Process • State in the OS In the kernel (a.out) $./a.out • Kernel stack space – State contains : registers, list of open files, related processes, etc. 2 Program ≠ Process Program Process code + static and global data Dynamic instantiation of code + data + heap + stack + process state One program can create several A process is unique isolated entity processes 3 Process Address Space • Virtual Address Map MAX_SIZE – All memory a process can Stack address – Large contiguous array of addresses from 0 to Heap MAX_SIZE Data Text (instructions) 0 4 Process Address Space • Each process has a different address space • This is achieved by the use of virtual memory • Ie. 0 to MAX_SIZE are virtual memory addresses MAX_SIZE Stack Stack MAX_SIZE Heap Heap Data Data Process A Process B Process A Process B Page Table Text Text (instructions) (instructions) Page Table 0 0 5 Virtual Address Mapping Process A Process B Stack Stack Heap Heap Process A Process B Data Page Page Data Table Table Text Text (instructions) (instructions) Virtual Memory Physical Memory Virtual Memory 6 Advantages of Virtual Address Map • Isolation (private address space) – One process cannot access another process’ memory • Relocatable – Data and code within the process is relocatable • Size – Processes can be much larger than physical memory 7 Process Address Map in xv6 0xFE000000 • Entire kernel mapped into every process address space Kernel Text + Data, – This allows easy switching from DeviceMemory user code to kernel code (ie.
    [Show full text]
  • Specification and Analysis of Resource Utilization Policies for Human-Intensive Systems
    University of Massachusetts Amherst ScholarWorks@UMass Amherst Doctoral Dissertations Dissertations and Theses November 2016 Specification and Analysis of Resource Utilization Policies for Human-Intensive Systems Seung Yeob Shin University of Massachusetts - Amherst Follow this and additional works at: https://scholarworks.umass.edu/dissertations_2 Part of the Software Engineering Commons Recommended Citation Shin, Seung Yeob, "Specification and Analysis of Resource Utilization Policies for Human-Intensive Systems" (2016). Doctoral Dissertations. 805. https://scholarworks.umass.edu/dissertations_2/805 This Open Access Dissertation is brought to you for free and open access by the Dissertations and Theses at ScholarWorks@UMass Amherst. It has been accepted for inclusion in Doctoral Dissertations by an authorized administrator of ScholarWorks@UMass Amherst. For more information, please contact [email protected]. SPECIFICATION AND ANALYSIS OF RESOURCE UTILIZATION POLICIES FOR HUMAN-INTENSIVE SYSTEMS A Dissertation Presented by SEUNG YEOB SHIN Submitted to the Graduate School of the University of Massachusetts Amherst in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY September 2016 Computer Science c Copyright by Seung Yeob Shin 2016 All Rights Reserved SPECIFICATION AND ANALYSIS OF RESOURCE UTILIZATION POLICIES FOR HUMAN-INTENSIVE SYSTEMS A Dissertation Presented by SEUNG YEOB SHIN Approved as to style and content by: Leon J. Osterweil, Co-chair Yuriy Brun, Co-chair Lori A. Clarke, Member George S. Avrunin, Member Hari Balasubramanian, Member James Allan, Chair of the Faculty College of Information and Computer Sciences DEDICATION To my family ACKNOWLEDGMENTS First and foremost, I would like to express my sincere gratitude to my advisors: Leon J. Osterweil and Yuriy Brun.
    [Show full text]