8.7. In the VAX, user page tables are located at virtual addresses in the system space. What is the advantage of having user page tables in virtual rather than main memory? What is the disadvantage?
8.7. In the VAX, user page tables are located at virtual addresses in the system space. What is the advantage of having user page tables in virtual rather than main memory? What is the disadvantage?
Chapter11: Operating Systems
Section: Chapter Questions
Problem 21VE
Related questions
Question

Transcribed Image Text:**8.9. IBM System/370 Architecture Overview**
The IBM System/370 architecture utilizes a two-level memory structure, often described as segments and pages. Although this segmentation approach lacks several features mentioned earlier in this chapter, it serves a purpose in memory management.
For the basic 370 architecture:
- The page size can be either 2 KB or 4 KB.
- The segment size is fixed at either 64 KB or 1 MB.
For the 370/XA and 370/ESA architectures:
- The page size is standardized at 4 KB.
- The segment size is fixed at 1 MB.
**Discussion Points:**
- What are the potential disadvantages of this segmentation scheme?
- What benefits does segmentation offer to the 370 architecture?

Transcribed Image Text:**8.7.** In the VAX, user page tables are located at virtual addresses in the system space. What is the advantage of having user page tables in virtual rather than main memory? What is the disadvantage?
*Explanation:*
In the VAX computer architecture, user page tables can be stored at virtual addresses within the system space rather than directly in main memory. This setup has certain advantages and disadvantages:
**Advantages:**
1. **Increased Flexibility:** By using virtual addresses, the system can more flexibly manage memory, allowing for more efficient use of available memory resources.
2. **Protection:** Storing page tables at virtual addresses can improve protection against unauthorized access, as it enables the system to apply access controls and permissions more effectively.
**Disadvantages:**
1. **Additional Overhead:** Managing page tables at virtual addresses can introduce additional computational overhead, as it requires translating virtual addresses to physical addresses.
2. **Potential For Increased Latency:** Accessing page tables in virtual memory might increase latency compared to direct access in physical memory, potentially affecting system performance.
Expert Solution

This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps

Knowledge Booster
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.Recommended textbooks for you

Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning

C++ for Engineers and Scientists
Computer Science
ISBN:
9781133187844
Author:
Bronson, Gary J.
Publisher:
Course Technology Ptr

Operations Research : Applications and Algorithms
Computer Science
ISBN:
9780534380588
Author:
Wayne L. Winston
Publisher:
Brooks Cole

Systems Architecture
Computer Science
ISBN:
9781305080195
Author:
Stephen D. Burd
Publisher:
Cengage Learning

C++ for Engineers and Scientists
Computer Science
ISBN:
9781133187844
Author:
Bronson, Gary J.
Publisher:
Course Technology Ptr

Operations Research : Applications and Algorithms
Computer Science
ISBN:
9780534380588
Author:
Wayne L. Winston
Publisher:
Brooks Cole

Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning

C++ Programming: From Problem Analysis to Program…
Computer Science
ISBN:
9781337102087
Author:
D. S. Malik
Publisher:
Cengage Learning

Microsoft Visual C#
Computer Science
ISBN:
9781337102100
Author:
Joyce, Farrell.
Publisher:
Cengage Learning,