Preview. Memory Management

Transcription

1 Preview Memory Management With Mono-Process With Multi-Processes Multi-process with Fixed Partitions Modeling Multiprogramming Swapping Memory Management with Bitmaps Memory Management with Free-List Virtual Memory Virtual Memory with Paging Page Table Multilevel Page Table CS 431 Operating Systems 1

2 Memory Management Ideal Memory Infinitely Large Infinitely Fast Non-volatile Inexpensive No such a memory, most computers has a memory hierarchy Memory hierarchy Small, fast, very expensive registers Volatile, expensive cache memory Megabyte medium-speed, medium-speed RAM Tens or hundreds of gigabits of slow cheap, non-volatile disk storage (Hard Disks) Memory management is a part of the operating system which manages the memory hierarchy CS 431 Operating Systems 2

3 Memory Management (mono-process) Mono-programming without Swapping or Paging There is only memory sharing between a user program and the operating system in this system. Only one program could be loaded in the memory. When the program finishes its job, a scheduler (long term scheduler) chooses one job from the pool of jobs and loads it into the memory and starts to run. CS 431 Operating Systems 3

4 Memory Management (mono-process) CS 431 Operating Systems 4

5 Memory Management (multi-process) Multiprogramming with Fixed Partition - Memory is divided into n (possibly unequal size) partitions can be done manually when the system started. 1. Fixed memory partitions with separate input queues for each partition 2. Fixed memory partitions with a single input queue. CS 431 Operating Systems 5

6 Memory Management (multi-process with fixed partition) CS 431 Operating Systems 6

7 Memory Management (multi-process with fixed partition) Fixed memory partitions with separate input queues for each partition When a job arrives, it can be put into the queue for the smallest partition that is large enough to hold it. Disadvantage Large partition queue is empty but many small jobs are waiting on the small partition queue. CS 431 Operating Systems 7

8 Memory Management (multi-process with fixed partition) Fixed memory partitions with a single input queue. Whenever a partition becomes free, the closest to the queue that fits in it, is chosen and loaded into the empty partition and run wasting memory. Or Search the whole queue to find out a job which is the best fit to the free partition. discriminate against small jobs. One partition for small jobs Count the time skipped by scheduler. If a job was skipped more than k time, it is automatically granted next time. CS 431 Operating Systems 8

9 Modeling Multiprogramming Simple Unrealistic Model Assumption: all five processes will never be waiting for I/O at the same time If the average processes use 20% computing time and 80% use for waiting I/O. With five processes in the memory at once, the CPU should be busy 100% CS 431 Operating Systems 9

10 Modeling Multiprogramming Probabilistic model p - a fraction of time a process is waiting for I/O. If there are n processes in the memory at once, the probability that all n processes are waiting for I/O is p n. Then, the CPU utilization is given by CPU utilization = 1 p n (the probability that at least one of processes is using CPU) CS 431 Operating Systems 10

11 Modeling Multiprogramming CS 431 Operating Systems 11

12 Modeling Multiprogramming Ex) A computer has 32MB of memory, with operating system taking up 16 MB and each program taking up 4MB. 4 programs to be in memory at once (4 X 4 = 16MB). With an 80 % average I/O wait, we can have about 60 % of CPU utilization. Adding 16MB memory, (4 more programs: a total of 8 programs to be in the memory) we can get about 83% of CPU utilization. Adding yet another 16MB memory, (a total of 12 programs to be in the memory) we can get about 93% of CPU utilization CS 431 Operating Systems 12

13 Memory Management There is not enough main memory to hold all the currently active processes, so excess processes must be kept on disk and brought in to run dynamically. Two general approaches for memory management (depending on the available hardware) 1. Swapping bringing in each process in its entirety, running it for a while, then putting it back on the disk. 2. Virtual Memory allows programs to run while partially loaded in the memory. CS 431 Operating Systems 13

14 Swapping with Variable Partition CS 431 Operating Systems 14

15 Swapping Main difference between fixed partition and variable partition Variable partition The number, location, and size of the partitions vary dynamically Need to keep track of partition information dynamically for memory allocation and de-allocation Might create multiple holes Combine them all into one big hole (memory compaction: expensive cycle) Fixed partition The number, location, and size of the partitions fixed. OS knows the address of each process. Simple to manage the memory. CS 431 Operating Systems 15

16 Swapping How much memory should be allocated for a process when it is created or swapped? If processes are created with a fixed size simple But processes are usually changing their sizes by dynamically allocating memory Dynamic memory allocation (heap), recursion Allocate extra memory space for each process Use adjacent hole for managing the growing size If there is not enough memory space for a process based on the dynamically changing size, the process might be swapped out or killed. CS 431 Operating Systems 16

17 Swapping CS 431 Operating Systems 17

18 Memory Management with Bitmaps Memory is divided up into allocation units (words ~ k bytes) Corresponding to each allocation unit is a bit in the bitmap If the unit is free, corresponding bit = 0 and If unit is occupied, corresponding bit = 1. CS 431 Operating Systems 18

19 Memory Management with Bitmaps CS 431 Operating Systems 19

20 Memory Management with Bitmaps Size of the allocation unit is an important design issue The smaller the allocation unit, the larger the bitmap. The larger the allocation unit, the smaller the bitmap But memory may be wasted in the last unit of the process if the process size is not an exact multiple of the allocation unit. CS 431 Operating Systems 20

21 Memory Management with Bitmaps Advantage with Bitmaps Simple way to keep track of memory words in a fixed amount of memory since the size of bitmap depends only on the size of memory and size of the allocation units. Disadvantage with Bitmaps To allocate memory for the process with k unit size, first, the memory manager needs to search the bitmap to find out k consecutive 0 bits in the map. CS 431 Operating Systems 21

22 Memory Management with Free-List With free-list, maintain a linked list of allocated and free memory segments. Each entry in the list keeps information: hole or process, starting address, length and a pointer to the next entry P 0 5 H 5 3 CS 431 Operating Systems 22

23 Memory Management with Free-List CS 431 Operating Systems 23

24 Memory Management with Free-List If the list of segments is kept sorted by address value, it is simple to update the list when a process terminates or is swapped out from memory. CS 431 Operating Systems 24

25 Memory Management with Free-List CS 431 Operating Systems 25

26 Memory Management with Free-List CS 431 Operating Systems 26

27 Memory Management with Free-List Algorithms for allocating memory for a process (Assume that the list of segments is kept sorted by address value). First Fit The memory manager scans the list of segments from the beginning until it finds a hole that is big enough. Next Fit It works the same way as first fit. But next time it is called, it starts searching the list from the place where it left off last time. Best Fit It searches the entire list and takes the smallest hole that fit for the process. Worst Fit It always takes the largest free hole CS 431 Operating Systems 27

28 Memory Management with Free-List Four algorithms can be more efficient by maintaining two lists: one for holes and another for processes. The list of holes can be maintained sorted by size. Best fit does not need to search entire list. But still need extra effort for updating two lists based on the allocation and deallocation of memory. CS 431 Operating Systems 28

29 Memory Management with Free-List Quick Fit Maintains separate lists for holes based on the size. It might have a table with n entries. Each entry is a pointer to the head of a certain size of holes list. Ex) First entry point to the head of list of 4-KB holes, second entry point to the head of list of 8-KB holes,. Quick to finding a hole of required size Expensive to maintain the separate lists for hole based on the deallocation of memory CS 431 Operating Systems 29

30 Virtual Memory Motivation Initial idea of executing a program is that the entire logical address space of a process must be in physical memory before the process can access (swapping). But since size of a program grows tremendously based on the complexity of modern software, and limited size of physical memory, initial idea is not possible. CS 431 Operating Systems 30

31 Virtual Memory Overlay Split a program into pieces (overlays) Overlay 0 starts running first; when it finishes its job, it will call another overlay. Overlays were kept on the disk and swapped in and out of memory by OS. The work of splitting the program into pieces had to be done by programmer. Splitting up large program into small pieces is time consuming. CS 431 Operating Systems 31

32 Virtual Memory Virtual Memory Virtual memory is a technique that allows the execution of processes that may not be entirely in memory The OS needs to keep track of the parts of the program currently located in main memory and the rest on the disk. Virtual memory idea can be used in a multiprogramming system. CS 431 Operating Systems 32

33 Virtual Memory with Paging Paging Virtual address space is divided into units called pages. The corresponding units in the physical memory is called page frames. the size of a page = the size of a page frame Size of page is usually between 512 byte and 64KB CS 431 Operating Systems 33

34 Virtual Memory with Paging Mapping from Virtual Memory Address to Physical Memory Address When virtual memory is used, a virtual address (which is generated by a program) does not go directly onto the memory bus. Instead, they goes to an MMU (Memory Management Unit) that maps the virtual addresses onto the physical memory addresses based on the memory map (page table). CS 431 Operating Systems 34

35 Virtual Memory with Paging CS 431 Operating Systems 35

36 Virtual Memory with Paging Example) A computer that can generate 16-bit address 64KB virtual space (0 ~ = 0 ~ ) A system is using the virtual memory with page size 4KB A computer has 32 KB memory There are 16 virtual pages and 8 (32/4) page frames. CS 431 Operating Systems 36

37 Virtual Memory with Paging CS 431 Operating Systems 37

38 Virtual Memory with Paging MOV REG, 0 ;; (move content of address 0 to register.) virtual address 0 is sent to MMU. MMU checks virtual address, 0 belongs to virtual page 0 (0 ~ 4095 (= ). MMU checks memory map such that page 0 is mapped to page frame 2 (8K ~ 12K) MMU sends 8192 (= 2 13 ) physical address to address bus. CS 431 Operating Systems 38

39 Virtual Memory with Paging MOV REG, 8900 ;; Virtual address 8900 is send to MMU MMU calculates the virtual address 8900 that belongs to virtual page 2 (=between 8 KB ~ 12 KB) (8192~12287) MMU checks memory map such that virtual page 2 is mapped to physical frame 6 (24KB ~ 28 KB) (24576 ~28671) MMU sends the address ( ) = (physical address) to address CS 431 Operating Systems 39

40 Virtual Memory with Paging MOV REG Virtual address is sent to MMU MMU calculates the virtual address belongs to virtual page 6 (=between 24 KB ~ 28 KB: ~28671 ) MMU checks memory map such that virtual page 6 is not in physical space yet. (page fault) When a page fault occurs, operating system picks one of physical frame write back to disk fetch the page to the frame just freed change the memory map CS 431 Operating Systems 40

41 Virtual Memory with Paging CS 431 Operating Systems 41

42 Virtual Memory with Paging How to map virtual address into physical address by MMU with Previous Example The incoming 16-bit address is split into 4-bit page number and 12bit offset. With 4-bit page number, 2 4 = 16 page number is available. The 4-bit page number is used as an index in the page table, With 12-bits offset, we can address 2 12 = 4KB within a page. CS 431 Operating Systems 42

43 Virtual Memory with Paging CS 431 Operating Systems 43

44 Page Table The purpose of the page table is to map virtual pages onto page frames. Two major issues of using page table The page table can be extremely large The mapping must be fast CS 431 Operating Systems 44

45 Page Table The page table can be extremely large Ex) A modern computer with 32-bit virtual address and 4 KB page size 2 32 = 2 22 KB virtual space 2 22 / 4 = pages Need entries in the page table Since each process has its own virtual space, each process needs its own page table.!!! CS 431 Operating Systems 45

46 Page Table The mapping must be fast Build a single table consisting of an array of fast hardware registers, with one entry for each virtual page, indexed by virtual page number. --- very expensive!! The page table can be entirely in main memory all the hardware needs is a single register that points to the start of the page table --- needs one or more memory references to read page table entries. CS 431 Operating Systems 46

47 Multilevel Page Table The basic idea of multilevel page table method is to avoid keeping the complete page tables in memory all the time!!! Ex) A system is using second level page tables The system generates 32-bit virtual address with a page size of 4KB. We have a 32-bit virtual address which is partitioned into 10-bit PT1 field 10-bit PT2 field 12-bit offset field (for page size 4KB) PT1 PT2 Offset Since offset is 12 bits, pages are 4KB and there are totally 2 20 of them. CS 431 Operating Systems 47

48 2 10 entries for top level page table 2 10 entries for each of second level page table Address space for second level page table is 4 KB 2 10 = 4 MB CS 431 Operating Systems 48

49 Multilevel Page Table Ex) virtual address (= = ) PT1 = = 1 10 PT2 = = 3 10 Offset = = 4 10 CS 431 Operating Systems 49

50 Multilevel Page Table The MMU uses PT1 to index into the top-level page table and obtain entry 1 ( ) (physical address between 4M ~ 8M). Then the MMU uses PT2 to index into the secondlevel page table and obtain entry 3 ( ) (Corresponds to address 12 K ~ 16 K within 4M chunk = ~ 16383) = (address between 4M + 12K ~ 4M + 16K 1 = ~ ) If the page is in the memory, the page frame number taken from the second-level page table is combined with the offset (4) to construct a physical address. CS 431 Operating Systems 50