 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| n |
Page size is
defined by hardware; always a
|
|
|
power of 2
for more efficient logical to physical
|
|
|
address
translation. But exactly which size to
|
|
|
use is a
difficult question:
|
|
|
|
u |
Large page size
is good since for a small page size,
|
|
|
more pages are
required per process
|
|
|
|
F |
More pages per
process means larger page tables.
|
|
|
Hence, a large
portion of page tables in virtual memory
|
|
|
|
u |
Small page size
is good to minimize internal
|
|
|
fragmentation
|
|
|
|
u |
Large page size
is good since disks are designed to
|
|
|
|
efficiently transfer large blocks of data
|
|
|
|
u |
Larger page
sizes means less pages in main memory;
|
|
|
this increases
the TLB hit ratio
|
|
