Skip to content Skip to navigation

Connexions

You are here: Home » Content » Project 4: Emand Paging

Navigation

Lenses

What is a lens?

Definition of a lens

Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

This content is ...

Affiliated with (What does "Affiliated with" mean?)

This content is either by members of the organizations listed or about topics related to the organizations listed. Click each link to see a list of all content affiliated with the organization.
  • VOCW

    This module is included inLens: Vietnam OpenCourseWare's Lens
    By: Vietnam OpenCourseWare

    Click the "VOCW" link to see all content affiliated with them.

Recently Viewed

This feature requires Javascript to be enabled.
 

Project 4: Emand Paging

Module by: Duong Anh Duc. E-mail the author

Summary: Operating Systems One-month project

The third Nachos project is to build a demand paging system. You will create the mechanisms and policies for a demand paging system with a simple page table system. You will also implement a simple page replacement algorithm.

Phase 1: Understand the Code

You will modify the set of files that you have after completion of projects 1. It is important that you understand how the demand paging and address translation system in Nachos works. To this end, we suggest that you examine the following files:

machine.* : We will not use TLB. We will compile in the vm directory to make use of the

dependency setting stated in the Makefile there. Remove USE_TLB flag from the lines stating the various components used.

translate.* : Examine the ReadMem, WriteMem, and Translate methods of machine. It is important to understand how a PageFaultException is generated for a page miss. Pay particular attention to where the invalid virtual address is stored when the exception occurs, since you will need to access it later.

addrspace.* : The role of address space will change, but it is now important to understand what ALL of the methods do, not just the constructor or deconstructor.

exception.cc : The majority of your demand paging code will be called from the PageFaultException handler.

bitmap.* : routines for manipulating bitmaps

filesys.h

openfile.h : Pay careful attention to the readAt and writeAt methods!

../test/* : C programs that will be cross-compiled to MIPS and run in Nachos

Phase 2 : Design Considerations

When the machine object is instantiated, the pagetable will be initialized with all entries invalid. This will generate a page fault when the first memory address is accessed. The majority of your design will deal with what happens when a page fault occurs.

In order to implement full demand paging, you will also be required to create and modify several other data structures. Such data structures include:

  • Modification of the TranslationEntry data structure to support a reference word.
  • A method for determining the source and destination expression for the page to be loaded, from a file to the main memory.

You will also have to account for all phases of the demand paging algorithm. These phases include:

  • Page Table Hit
  • Page Table Miss, free entry in the main memory
  • Page Table Miss, page replacement in the main memory, replacement page clean, and
  • Page Table Miss, page replacement in the main memory, replacement entry dirty.

You should also make sure that you separate the mechanisms and policies. Initially you will use FIFO policy for replacement. After testing pagefault handler with FIFO, replace it with LRU page replacement algorithm.

Phase 3: [90%] Lab 3 Assignment

NOTE: It is very important to compile this project in the VM directory! Your files will be in userprog.

  • Understand Page Tables – This is very important, but will not count towards your grade.
  • Change Constants in machine.h – Please change the constants in machine.h to the following:NumPhysPages32
  • Change class TranslationEntry in translate.h – Add ‘int refword’ as an instance variable to this class (under the dirty bit)
  • Moving pages in and out of main memory: A critical step in the demand paging in rolling pages needed from an executable file into the main memory and rolling out dirty pages back to the file. It is suggested that you write a helper class that will exclusively focus on these operations. For more information on the code look at address space constructor.
  • Data structure for the Page Table – Base the design of the page table on the TranslationEntry class. You may need to add an extra entry for page replacement policy.
  • Implement FIFO Page Table Demand Paging – You must now process all PageFaultExpections, and implement the core demand paging algorithm. After complete testing use LRU method.
  • Design three user programs that can be run inside the shell to demonstrate the robustness of your overall project solution.

Phase 4: [10%] Documentation

Answer the following questions in brief:

1. Describe the steps that occur during a Page Fault Exception when: (6)      a. There are free pages in the main memory

      b. There are NO free pages in the main memory & dirty bit for the replacement page is NOT set.

      c. There are NO free pages in the main memory & dirty bit for the replacement page is SET.

2. Give an example of LRU & FIFO policies.(2)

3. Where exactly have you updated the reference count for the 2 policies & why specifically in these places? (Just give the function names & the reason)  (2)

Content actions

Download module as:

PDF | More downloads ...

Add module to:

My Favorites (?)

'My Favorites' is a special kind of lens which you can use to bookmark modules and collections. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need an account to use 'My Favorites'.

| A lens I own (?)

Definition of a lens

Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

| External bookmarks