A Theory of Indirection Via Approximation

Total Page:16

File Type:pdf, Size:1020Kb

A Theory of Indirection Via Approximation A Theory of Indirection via Approximation Aquinas Hobor ∗† Robert Dockins† Andrew W. Appel † National University of Singapore Princeton University Princeton University [email protected] [email protected] [email protected] Abstract Consider general references in the polymorphic λ-calculus. Building semantic models that account for various kinds of indirect Here is a flawed semantic model of types for this calculus: reference has traditionally been a difficult problem. Indirect refer- value ≡ loc of address + num of N + ... ence can appear in many guises, such as heap pointers, higher-order type ≡ (memtype × value) → T (1) functions, object references, and shared-memory mutexes. memtype ≈ address * type We give a general method to construct models containing indi- rect reference by presenting a “theory of indirection”. Our method Values are a tagged disjoint union, with the tag loc indicating can be applied in a wide variety of settings and uses only simple, a memory address. T is some notion of truth values (e.g., the elementary mathematics. In addition to various forms of indirect propositions of the metalogic or a boolean algebra) and a natural reference, the resulting models support powerful features such as interpretation of the type A → T is the characteristic function for a impredicative quantification and equirecursion; moreover they are set of A. We write ≈ to mean “we wish we could define things this compatible with the kind of powerful substructural accounting re- way” and A*B to indicate a finite partial function from A to B. quired to model (higher-order) separation logic. In contrast to pre- The typing judgment has the form ψ ` v : τ, where ψ is vious work, our model is easy to apply to new settings and has a a memory typing (memtype), v is a value, and τ is a type; the simple axiomatization, which is complete in the sense that all mod- semantic model for the typing judgment is ψ ` v : τ ≡ τ(ψ, v). els of it are isomorphic. Our proofs are machine-checked in Coq. Memory typings are partial functions from addresses to types. The motivation for this attempt is that the type “ref τ” can use the Categories and Subject Descriptors D.3.1 [PROGRAMMING memory typing to show that the reference’s location has type τ: LANGUAGES]: Formal Definitions and Theory — Semantics; F.3.1 [LOGICS AND MEANINGS OF PROGRAMS]: Specifying ref τ ≡ λ(ψ, v). ∃a. v = loc(a) ∧ ψ(a) = τ. and Verifying and Reasoning about Programs — Logics of pro- That is, a value v has type ref τ if it is an address a, and according grams; F.4.1 [MATHEMATICAL LOGIC AND FORMAL LAN- to the memory typing ψ, the memory cell at location a has type τ. GUAGES]: Mathematical Logic — Mechanical theorem proving Unfortunately, this series of definitions is not well-founded: type contains a contravariant occurrence of memtype, which in General Terms Languages, Theory, Verification turn contains an occurrence of type. A standard diagonalization Keywords Indirection theory, Step-indexed models proves that no solution to these equations exists in set theory. A recent approach to tackle this problem is to employ stratifi- cation, yielding a well-founded definition of an appropriate seman- 1. Introduction tic model [AAV03, Ahm04, AMRV07]. A key strength of these A recurring problem in the semantics of programming languages is models is that they can express general (impredicative) quantified finding semantic models for systems with indirect reference. Indi- types even though they are stratified. Unfortunately, these models rection via pointers gives us mutable records; indirection via locks have a disturbing tendency to “leak” into any proofs utilizing them, can be used for shared storage; indirection via code pointers gives making modularization difficult, obscuring their essential features, us complex patterns of computation and recursion. Models for pro- needlessly limiting their power, and contributing to unpleasant te- gram logics for these systems need to associate invariants (or asser- dium. Also, all of these models are specialized to the problem of tions, or types) with addresses in the store; and yet invariants are mutable references, and even for the expert it can be daunting to predicates on the store. Tying this “knot” has been difficult, espe- modify the techniques to apply to other domains. cially for program logics that support abstraction (impredicativity). Hobor et al. applied these techniques to Hoare logics, devel- oping a model for a concurrent separation logic (CSL) with first- ∗ Supported by a Lee Kuan Yew Postdoctoral Fellowship. class locks and threads [HAZ08]. This model was extremely com- † Supported in part by NSF awards CNS-0627650 and CNS-0910448, and plex to construct because the substructural accounting was woven AFOSR award FA9550-09-1-0138. throughout the stratification. It was also complex to use, exposing more than fifty axioms.Even then, the axiom set was incomplete: from time to time the CSL soundness proof required the statement and proof of additional properties (which were provable from the model). Like the mutable reference models, Hobor et al.’s model Permission to make digital or hard copies of all or part of this work for personal or was a solution to a specific problem, and could not be applied to classroom use is granted without fee provided that copies are not made or distributed other problems—not even to other concurrent separation logics. for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute We present a single solution, indirection theory, that can handle to lists, requires prior specific permission and/or a fee. these domains as well as numerous others. Our model is character- POPL’10, January 17–23, 2010, Madrid, Spain. ized by just two axioms, an order of magnitude better than the sim- Copyright c 2010 ACM 978-1-60558-479-9/10/01. $10.00 plest of the previous solutions. The axioms are equational, orthog- 1 onal, and complete, and have greater expressive power and cleaner 2.1 General references in the λ-calculus modularity. The modularity enables a graceful extension for sub- Ahmed et al. constructed the first model of a type system for the structural accounting that does not need to thread the accounting polymorphic λ-calculus with general references [AAV03]. Follow- through the stratification. Moreover, the axioms provide greater in- ing (1), we want a solution to the pseudoequation sight into the model by directly exposing the approximation at the heart of the stratification technique. memtype ≈ address * ((memtype × value) → T), As we show in §2, a key observation is that many domains can which falls neatly into the pattern of pseudoequation (2) with be described by the pseudoequation: F (X) ≡ address *X K ≈ F ((K × O) → ), (2) T O ≡ value. where F (X) is a covariant functor, O is some arbitrary set of By equation (3), indirection theory constructs the approximation “other” data and K is the object that we wish to construct. The earlier cardinality argument guarantees we cannot construct K (in memtype N × (address * ((memtype × value) → T)), set theory), but indirection theory lets us approximate it: and by folding the definition of type (from eqn. 1) we reach K N × F ((K × O) → T) (3) memtype N × (address * type). Here X Y means the “small” type X is related to the “big” type This model is sufficient to define a powerful type system for the Y by two functions: squash : Y → X and unsquash : X → Y . polymorphic λ-calculus with mutable references. In §4.1, we will The squash function “packs” an element y of the big type Y into an show how to construct the types nat and ref τ. element of the small type X, applying an approximation when the structure of y is too complex to fit into X. The unsquash function 2.2 General references in von Neumann machines reverses the process, “unpacking” an element of X into an element Modeling a type system with general references for von Neumann of Y ; since Y is bigger than X, unsquash is lossless. machines was solved first by Ahmed [Ahm04], and then later in The squash and unsquash functions form a section-retraction a more sophisticated way by Appel et al. [AMRV07]. The key is pair, meaning that squash ◦ unsquash : X → X is the identity that whereas in the λ-calculus types are based on sets of values, on function and unsquash ◦ squash : Y → Y is an approximation a von Neumann machine types are based on sets of register banks. function. Thus X Y is almost an isomorphism, and informally Here is the intuition for a von Neumann machine with 32-bit integer one can read X Y as “X is approximately Y”. With equation memory addressing and m 32-bit integer registers: (3), indirection theory says that left hand side of pseudoequation m−2 (2) is approximately equal to a pair of a natural number and the rbank ≡ int32× ... ×int32 right hand side of pseudoequation (2). type ≡ (memtype × rbank) → T memtype ≈ int32 * type. Contributions. The intuition is thus very similar to the λ-calculus case. We set §2 We show numerous examples containing indirect reference and F (X) ≡ int32 *X show how they can be characterized with a covariant functor. O ≡ rbank, §3 We present the two axioms of indirection theory. and indirection theory constructs the approximation §4 We show how to apply the axioms to two of the examples. memtype N × (int32 * type). §5 We explore some implications of indirection theory. In the λ-calculus, the memory maps addresses to values, and values §6 We induce an impredicative logic from indirection theory.
Recommended publications
  • CWIC: Using Images to Passively Browse the Web
    CWIC: Using Images to Passively Browse the Web Quasedra Y. Brown D. Scott McCrickard Computer Information Systems College of Computing and GVU Center Clark Atlanta University Georgia Institute of Technology Atlanta, GA 30314 Atlanta, GA 30332 [email protected] [email protected] Advisor: John Stasko ([email protected]) Abstract The World Wide Web has emerged as one of the most widely available and diverse information sources of all time, yet the options for accessing this information are limited. This paper introduces CWIC, the Continuous Web Image Collector, a system that automatically traverses selected Web sites collecting and analyzing images, then presents them to the user using one of a variety of available display mechanisms and layouts. The CWIC mechanisms were chosen because they present the images in a non-intrusive method: the goal is to allow users to stay abreast of Web information while continuing with more important tasks. The various display layouts allow the user to select one that will provide them with little interruptions as possible yet will be aesthetically pleasing. 1 1. Introduction The World Wide Web has emerged as one of the most widely available and diverse information sources of all time. The Web is essentially a multimedia database containing text, graphics, and more on an endless variety of topics. Yet the options for accessing this information are somewhat limited. Browsers are fine for surfing, and search engines and Web starting points can guide users to interesting sites, but these are all active activities that demand the full attention of the user. This paper introduces CWIC, a passive-browsing tool that presents Web information in a non-intrusive and aesthetically pleasing manner.
    [Show full text]
  • Virtual Memory
    Topic 18: Virtual Memory COS / ELE 375 Computer Architecture and Organization Princeton University Fall 2015 Prof. David August 1 Virtual Memory Any time you see virtual, think “using a level of indirection” Virtual memory: level of indirection to physical memory • Program uses virtual memory addresses • Virtual address is converted to a physical address • Physical address indicates physical location of data • Physical location can be memory or disk! 0x800 Disk:Mem: 0x803C4 0x3C00 Virtual address Physical address 2 Virtual Memory 3 Virtual Memory 1 4 Virtual Memory: Take 1 Main memory may not be large enough for a task • Programmers turn to overlays and disk • Many programs would have to do this • Programmers should have to worry about main memory size across machines Use virtual memory to make memory look bigger for all programs 5 A System with Only Physical Memory Examples: Most Cray machines, early PCs, nearly all current embedded systems, etc. Memory 0: 1: Store 0x10 CPU Load 0xf0 N-1: CPU’s load or store addresses used directly to access memory. 6 A System with Virtual Memory Examples: modern workstations, servers, PCs, etc. Memory 0: Page Table 1: Virtual Physical Addresses 0: Addresses 1: Store 0x10 CPU Load 0xf0 P-1: N-1: Disk Address Translation: the hardware converts virtual addresses into physical addresses via an OS-managed lookup table (page table) 7 Page Faults (Similar to “Cache Misses”) What if an object is on disk rather than in memory? 1. Page table indicates that the virtual address is not in memory 2. OS trap handler is invoked, moving data from disk into memory • Current process suspends, others can resume • OS has full control over placement, etc.
    [Show full text]
  • Concept-Oriented Programming: References, Classes and Inheritance Revisited
    Concept-Oriented Programming: References, Classes and Inheritance Revisited Alexandr Savinov Database Technology Group, Technische Universität Dresden, Germany http://conceptoriented.org Abstract representation and access is supposed to be provided by the translator. Any object is guaranteed to get some kind The main goal of concept-oriented programming (COP) is of primitive reference and a built-in access procedure describing how objects are represented and accessed. It without a possibility to change them. Thus there is a makes references (object locations) first-class elements of strong asymmetry between the role of objects and refer- the program responsible for many important functions ences in OOP: objects are intended to implement domain- which are difficult to model via objects. COP rethinks and specific structure and behavior while references have a generalizes such primary notions of object-orientation as primitive form and are not modeled by the programmer. class and inheritance by introducing a novel construct, Programming means describing objects but not refer- concept, and a new relation, inclusion. An advantage is ences. that using only a few basic notions we are able to describe One reason for this asymmetry is that there is a very many general patterns of thoughts currently belonging to old and very strong belief that it is entity that should be in different programming paradigms: modeling object hier- the focus of modeling (including programming) while archies (prototype-based programming), precedence of identities simply serve entities. And even though object parent methods over child methods (inner methods in identity has been considered “a pillar of object orienta- Beta), modularizing cross-cutting concerns (aspect- tion” [Ken91] their support has always been much weaker oriented programming), value-orientation (functional pro- in comparison to that of entities.
    [Show full text]
  • Technical Manual Version 8
    HANDLE.NET (Ver. 8) Technical Manual HANDLE.NET (version 8) Technical Manual Version 8 Corporation for National Research Initiatives June 2015 hdl:4263537/5043 1 HANDLE.NET (Ver. 8) Technical Manual HANDLE.NET 8 software is subject to the terms of the Handle System Public License (version 2). Please read the license: http://hdl.handle.net/4263537/5030. A Handle System Service ​ ​ Agreement is required in order to provide identifier/resolution services using the Handle System technology. Please read the Service Agreement: http://hdl.handle.net/4263537/5029. ​ ​ © Corporation for National Research Initiatives, 2015, All Rights Reserved. Credits CNRI wishes to thank the prototyping team of the Los Alamos National Laboratory Research Library for their collaboration in the deployment and testing of a very large Handle System implementation, leading to new designs for high performance handle administration, and handle users at the Max Planck Institute for Psycholinguistics and Lund University Libraries ​ ​ ​ NetLab for their instructions for using PostgreSQL as custom handle storage. ​ Version Note Handle System Version 8, released in June 2015, constituted a major upgrade to the Handle System. Major improvements include a RESTful JSON-based HTTP API, a browser-based admin client, an extension framework allowing Java Servlet apps, authentication using handle identities without specific indexes, multi-primary replication, security improvements, and a variety of tool and configuration improvements. See the Version 8 Release Notes for details. Please send questions or comments to the Handle System Administrator at [email protected]. 2 HANDLE.NET (Ver. 8) Technical Manual Table of Contents Credits Version Note 1 Introduction 1.1 Handle Syntax 1.2 Architecture 1.2.1 Scalability 1.2.2 Storage 1.2.3 Performance 1.3 Authentication 1.3.1 Types of Authentication 1.3.2 Certification 1.3.3 Sessions 1.3.4 Algorithms TODO 3 HANDLE.NET (Ver.
    [Show full text]
  • Pointers Getting a Handle on Data
    3RLQWHUV *HWWLQJ D +DQGOH RQ 'DWD Content provided in partnership with Prentice Hall PTR, from the book C++ Without Fear: A Beginner’s Guide That Makes You Feel Smart, 1/e by Brian Overlandà 6 Perhaps more than anything else, the C-based languages (of which C++ is a proud member) are characterized by the use of pointers—variables that store memory addresses. The subject sometimes gets a reputation for being difficult for beginners. It seems to some people that pointers are part of a plot by experienced programmers to wreak vengeance on the rest of us (because they didn’t get chosen for basketball, invited to the prom, or whatever). But a pointer is just another way of referring to data. There’s nothing mysterious about pointers; you will always succeed in using them if you follow simple, specific steps. Of course, you may find yourself baffled (as I once did) that you need to go through these steps at all—why not just use simple variable names in all cases? True enough, the use of simple variables to refer to data is often sufficient. But sometimes, programs have special needs. What I hope to show in this chapter is why the extra steps involved in pointer use are often justified. The Concept of Pointer The simplest programs consist of one function (main) that doesn’t interact with the network or operating system. With such programs, you can probably go the rest of your life without pointers. But when you write programs with multiple functions, you may need one func- tion to hand off a data address to another.
    [Show full text]
  • KTH Introduction to Opencl
    Introduction to OpenCL David Black-Schaffer [email protected] 1 Disclaimer I worked for Apple developing OpenCL I’m biased Please point out my biases. They help me get a better perspective and may reveal something. 2 What is OpenCL? Low-level language for high-performance heterogeneous data-parallel computation. Access to all compute devices in your system: CPUs GPUs Accelerators (e.g., CELL… unless IBM cancels Cell) Based on C99 Portable across devices Vector intrinsics and math libraries Guaranteed precision for operations Open standard Low-level -- doesn’t try to do everything for you, but… High-performance -- you can control all the details to get the maximum performance. This is essential to be successful as a performance- oriented standard. (Things like Java have succeeded here as standards for reasons other than performance.) Heterogeneous -- runs across all your devices; same code runs on any device. Data-parallel -- this is the only model that supports good performance today. OpenCL has task-parallelism, but it is largely an after-thought and will not get you good performance on today’s hardware. Vector intrinsics will map to the correct instructions automatically. This means you don’t have to write SSE code anymore and you’ll still get good performance on scalar devices. The precision is important as historically GPUs have not cared about accuracy as long as the images looked “good”. These requirements are forcing them to take accuracy seriously.! 3 Open Standard? Huge industry support Driving hardware requirements This is a big deal. Note that the big three hardware companies are here (Intel, AMD, and Nvidia), but that there are also a lot of embedded companies (Nokia, Ericsson, ARM, TI).
    [Show full text]
  • Operating System
    OPERATING SYSTEM INDEX LESSON 1: INTRODUCTION TO OPERATING SYSTEM LESSON 2: FILE SYSTEM – I LESSON 3: FILE SYSTEM – II LESSON 4: CPU SCHEDULING LESSON 5: MEMORY MANAGEMENT – I LESSON 6: MEMORY MANAGEMENT – II LESSON 7: DISK SCHEDULING LESSON 8: PROCESS MANAGEMENT LESSON 9: DEADLOCKS LESSON 10: CASE STUDY OF UNIX LESSON 11: CASE STUDY OF MS-DOS LESSON 12: CASE STUDY OF MS-WINDOWS NT Lesson No. 1 Intro. to Operating System 1 Lesson Number: 1 Writer: Dr. Rakesh Kumar Introduction to Operating System Vetter: Prof. Dharminder Kr. 1.0 OBJECTIVE The objective of this lesson is to make the students familiar with the basics of operating system. After studying this lesson they will be familiar with: 1. What is an operating system? 2. Important functions performed by an operating system. 3. Different types of operating systems. 1. 1 INTRODUCTION Operating system (OS) is a program or set of programs, which acts as an interface between a user of the computer & the computer hardware. The main purpose of an OS is to provide an environment in which we can execute programs. The main goals of the OS are (i) To make the computer system convenient to use, (ii) To make the use of computer hardware in efficient way. Operating System is system software, which may be viewed as collection of software consisting of procedures for operating the computer & providing an environment for execution of programs. It’s an interface between user & computer. So an OS makes everything in the computer to work together smoothly & efficiently. Figure 1: The relationship between application & system software Lesson No.
    [Show full text]
  • Herding Cats: Managing a Mobile UNIX Platform Maarten Thibaut and Wout Mertens – Cisco Systems
    Herding Cats: Managing a Mobile UNIX Platform Maarten Thibaut and Wout Mertens – Cisco Systems ABSTRACT Laptops running UNIX operating systems are gaining market share. This leads to more sysadmins being asked to support these systems. This paper describes the major technical decisions reached to facilitate the pilot roll out of a mobile Mac OS X platform. We explain which choices we made and why. We also list the main problems we encountered and how they were tackled. We show why in the environment of a customer support organization at Cisco, a file management tool with tripwire-like capabilities is needed. Radmind appears to be the only software base meeting these requirements. We show how the radmind suite can be extended and integrated to suit mobile clients in an enterprise environment. We provide solutions to automate asset tracking and the maintenance of encrypted home directory disk images. We draw conclusions and list the lessons learnt. Introduction Additional Material Mobile UNIX Platforms You can find additional material at http://rad- People have been using UNIX for more than 25 mind.org/contrib/LISA05 . There you’ll find: years. For much of that time computers running UNIX • The radmind extensions discussed in this paper were large, clunky machines that could only be called (distributed as patches) mobile if you happened to own a truck. The physical • The scripts called by cron to update the system location of the computer and its network address (radmind-update) and some scripts that toggle remained the same for much of the machine’s lifetime. radmind-update features Today we are faced with mass-produced UNIX • The login scripts enforcing the use of FileVault laptops that move around the world as fast as their • The asset database code (client and server) users do.1 • Various tidbits and scripts that could be of use Solutions specific to UNIX machines need to be to other system administrators put in place to handle UNIX laptop deployments in the • MCX configuration examples enterprise.
    [Show full text]
  • Chapter 9 Pointers
    Chapter 9 Pointers Objectives ❏ To understand the concept and use of pointers ❏ To be able to declare, define, and initialize pointers ❏ To write programs that access data through pointers ❏ To use pointers as parameters and return types ❏ To understand pointer compatibility, especially regarding pointers to pointers ❏ To understand the role of quality in software engineering Computer Science: A Structured Programming Approach Using C 1 FIGURE 9-1 Derived Types Computer Science: A Structured Programming Approach Using C 2 9-1 Introduction A pointer is a constant or variable that contains an address that can be used to access data. Pointers are built on the basic concept of pointer constants. Topics discussed in this section: Pointer Constants Pointer Values Pointer Variables Accessing Variables Through Pointers Pointer Declaration and Definition Declaration versus Redirection Initialization of Pointer Variables Computer Science: A Structured Programming Approach Using C 3 FIGURE 9-2 Character Constants and Variables Computer Science: A Structured Programming Approach Using C 4 FIGURE 9-3 Pointer Constants Computer Science: A Structured Programming Approach Using C 5 Note Pointer constants, drawn from the set of addresses for a computer, exist by themselves. We cannot change them; we can only use them. Computer Science: A Structured Programming Approach Using C 6 Note An address expression, one of the expression types in the unary expression category, consists of an ampersand (&) and a variable name. Computer Science: A Structured Programming Approach Using C 7 FIGURE 9-4 Print Character Addresses Computer Science: A Structured Programming Approach Using C 8 Note A variable’s address is the first byte occupied by the variable.
    [Show full text]
  • Mac OS X Server
    Mac OS X Server Version 10.4 Technology Overview August 2006 Technology Overview 2 Mac OS X Server Contents Page 3 Introduction Page 5 New in Version 10.4 Page 7 Operating System Fundamentals UNIX-Based Foundation 64-Bit Computing Advanced BSD Networking Architecture Robust Security Directory Integration High Availability Page 10 Integrated Management Tools Server Admin Workgroup Manager Page 14 Service Deployment and Administration Open Directory Server File and Print Services Mail Services Web Hosting Enterprise Applications Media Streaming iChat Server Software Update Server NetBoot and NetInstall Networking and VPN Distributed Computing Page 29 Product Details Page 31 Open Source Projects Page 35 Additional Resources Technology Overview 3 Mac OS X Server Introduction Mac OS X Server version 10.4 Tiger gives you everything you need to manage servers in a mixed-platform environment and to con gure, deploy, and manage powerful network services. Featuring the renowned Mac OS X interface, Mac OS X Server streamlines your management tasks with applications and utilities that are robust yet easy to use. Apple’s award-winning server software brings people and data together in innovative ways. Whether you want to empower users with instant messaging and blogging, gain greater control over email, reduce the cost and hassle of updating software, or build your own distributed supercomputer, Mac OS X Server v10.4 has the tools you need. The Universal release of Mac OS X Server runs on both Intel- and PowerPC-based The power and simplicity of Mac OS X Server are a re ection of Apple’s operating sys- Mac desktop and Xserve systems.
    [Show full text]
  • Pointers Pointers – Getting the Address of a Value the Address Operator (&) Returns the Memory Address of a Variable
    System Design and Programming II CSCI – 194 Section 01 CRN: 10968 Fall 2017 David L. Sylvester, Sr., Assistant Professor Chapter 9 Pointers Pointers – Getting the Address of a Value The address operator (&) returns the memory address of a variable. Every variable is allocated a section of memory large enough to hold a value of the variable data type. Commonly char one bytes shorts two bytes int, long, float four bytes double eight bytes Each byte of memory has a memory address. A variable’s address is the address of the first byte allocated to that variable. Ex: char letter; short number; float amount; letter number amount 1200 1201 1203 The addresses of the variables above are used as an example. Getting the address of a variable is accomplished by using the (&) operator in front of the variable name. It allows the system to return the address of that variable in hexadecimal. Ex: &amount //returns the variable’s address cout << &amount // displays the variable’s address Note: Do not confuse the address operator with the & symbol used when defining a referenced variable. Pointers – Sample Program // This program uses the & operator to determine a variable's // address and the sizeof operator to determine its size. #include <iostream> using namespace std; int main() { int x = 25; cout << "The address of x is " << &x << endl; cout << "The size of x is " << sizeof(x) << " bytes\n"; cout << "The value of x is "<< x << endl; } Sample output Pointers Variables Pointer variables or pointers, are special variables that hold a memory address. Just as int variables are designed to hold integers, pointers variables are designed to hold memory addresses.
    [Show full text]
  • Chapter 9: Memory Management
    Chapter 9: Memory Management I Background I Swapping I Contiguous Allocation I Paging I Segmentation I Segmentation with Paging Operating System Concepts 9.1 Silberschatz, Galvin and Gagne 2002 Background I Program must be brought into memory and placed within a process for it to be run. I Input queue – collection of processes on the disk that are waiting to be brought into memory to run the program. I User programs go through several steps before being run. Operating System Concepts 9.2 Silberschatz, Galvin and Gagne 2002 Binding of Instructions and Data to Memory Address binding of instructions and data to memory addresses can happen at three different stages. I Compile time: If memory location known a priori, absolute code can be generated; must recompile code if starting location changes. I Load time: Must generate relocatable code if memory location is not known at compile time. I Execution time: Binding delayed until run time if the process can be moved during its execution from one memory segment to another. Need hardware support for address maps (e.g., base and limit registers). Operating System Concepts 9.3 Silberschatz, Galvin and Gagne 2002 Multistep Processing of a User Program Operating System Concepts 9.4 Silberschatz, Galvin and Gagne 2002 Logical vs. Physical Address Space I The concept of a logical address space that is bound to a separate physical address space is central to proper memory management. ✦ Logical address – generated by the CPU; also referred to as virtual address. ✦ Physical address – address seen by the memory unit. I Logical and physical addresses are the same in compile- time and load-time address-binding schemes; logical (virtual) and physical addresses differ in execution-time address-binding scheme.
    [Show full text]