you are asked to develop a virtual memory simulation tool and do some experiments with it

you are asked to develop a virtual memory simulation tool and do some experiments with it. Your program will read a file called data.txt. This file consists of a long series of memory references. Each line of the file has three values, delimited by a space. The first field is an integer, showing the process number. The second is also an integer, showing a memory reference (address). And the third is a char, either “R” (Read) or “W” (Write). If this char is a “W”, it means that the referenced memory address is modified. Each memory reference happens in one time unit, i.e. every line in the data file should have a unique timestamp. The page table you maintain should also have a dirty bit and a reference bit for each page. You may want to include other data as well. All addresses are 16 bits; so all processes have a virtual address space of 64KB (216). All addresses read from the file will be in the range 0 ... 65535. Each page is 512 bytes, so each process has a page table of size 128 (216/29 ). In other words, in each virtual address, the first (most significant) 7 bits determine the virtual page number, and the last 9 bits determine the offset of the address within the page frame. There are 32 addressable physical pages in the main memory, i.e. the physical memory size is 32pages*512bytes/page = 16KB. You have to keep track of three statistics, the total number of page faults, the total number of disk references and the total number of dirty page writes. Every page fault has at least one disk reference, but if the page to be replaced is dirty, then there will be two disk references, one to copy the dirty page back to the disk and one to load the new page. Each process has its own page table, so address 12340 in process 1 is different from address 12340 in process 2. You should have a global variable debug. The user should be able to set this variable via command line. If debugging is on (debug == 1 or debug = True), your program should display information about each page fault whenever a page fault occurs. It should list the line that generated the page fault, the physical page being replaced, the process number, the virtual page, and whether or not the page being replaced was dirty.