CS604 - Operating Systems GDB No.1 Solution & Discussion Spring 2016 Due Date August 4, 2016
CS604 - Operating Systems GDB No. 1 Solution Spring 2016 Due Date August 4, 2016
Graded Discussion Board (GDB) will be launched on Wednesday, August 03, 2016 and it will close on Thursday, August 04, 2016.
Larger Page Tables can be implemented on Secondary storage devices which can excessively slow memory access. Give your concise comments to support or against the given statement?(Maximum 4 to 5 lines)
Please Discuss here about this GDB.Thanks
Our main purpose here discussion not just Solution
We are here with you hands in hands to facilitate your learning and do not appreciate the idea of copying or replicating solutions.
Any virtual memory system that has to make use of page files, swap files, or swap partitions because the application(s) require more memory than the computer has in RAM are potentially going to slow down the memory access.
With multiple applications running concurrently, this might not actually be a problem as the system can switch to a different application while it swaps memory pages to and from disk for an application that needs more memory space or has some pages swapped out to disk.
The amount of degradation will depend on the speed of the disk drives concerned and the speed of the interface that the disk drive(s) are using.
SSDs are probably best avoided as the potential for doing large numbers of writes exists and this can reduce the life of an SSD.
Tertiary storage (on tape or similar media) can really slow things down, and is rarely used nowadays.
I hope this helps.
this one is enough related to gdb topic
oyeeeeeee copy paste
In operating systems that use virtual memory, every process is given the impression that it is working with large, contiguous sections of memory. Physically, the memory of each process may be dispersed across different areas of physical memory, or may have been moved to storage, typically to a hard disk drive.
When a process requests access to data in its memory, it is the responsibility of the operating system to map the virtual address provided by the process to the physical address of the actual memory where that data is stored. The page table is where the operating system stores its mappings of virtual addresses to physical addresses, with each mapping also known as a page table entry. ..
kch aur is gdb k about
its totally irrelevant about this gdb
sir, if this is irrelevant then what is relevant ......
ye sahi nhi ha GDB ...
As the "secondary" in the question suggests and it is assumed that it is slower than primary memory it is shown here with example that large page tables can be written to secondary storage and hence has the potential of being slower.
Most often primary memory is referred to as DRAM and secondary memory is the disk with a magnitude higher in access times. When an application has demands on more memory in DRAM operating systems will take some of the unused memory (LRU) and write its contents into disks and then provide that space to the calling application. All of this is done in the context of the memory access request. when the original process who owned the memory tries to access it again then the memory subsystem performs a page fault leading to the handler in reading the contents of memory from secondary storage into primary and then completing the request to application. It maybe noted that this process of page fault does add to the additional latency in accessing memory. The aspect of performance penalty will be observed when the number of page faults are frequent enough that the operating system is constantly in the process of reading and writing contents to secondary storage i.e. a imbalance in system resources due to the application demand on the available resources
pages slows down tha secondry memory ?