Machine-translated by Google. Questions are authored in English.
Top

Discussion

Which of these is true of a page size that is very small?

  • A.The page table becomes large but internal fragmentation is low
  • B.Internal fragmentation increases
  • C.Disk transfers become more efficient
  • D.The TLB covers more of the address space

Answer: D

Correct answer: The page table becomes large but internal fragmentation is low

A small page size reduces internal fragmentation, since the waste is on average half a page per process. But it multiplies the number of pages, so the page table grows - consuming memory and requiring more levels of indirection. It also reduces TLB coverage: each TLB entry maps less of the address space, so a given program touches more entries and the miss rate rises. And disk transfers become less efficient, because the fixed cost of a seek is amortised over less data. A large page size reverses all four: smaller table, better TLB coverage, more efficient transfers, but more internal fragmentation and more data transferred that may never be used. The compromise most systems have settled on is 4 KB, with support for huge pages of 2 MB or 1 GB where a database or a virtual machine host benefits from the reduced TLB pressure. Page size is always a power of two, so that splitting an address into page number and offset requires no arithmetic.

No comment is present. Be the first to comment.
Loading…

Post your comment

Please log in or register to post a comment.