Kernel-Managed Swap Facility (KMSF) Manual

Introduction
Kernel-Managed Swap Facility (KMSF) Manual—425824-005
1-10
KMS Files and New Systems
•
Default swap files are not displayed in the NSKCOM opening banner, which only
displays configured swap files.
•
Default swap files are always Format 1 swap files.
•
The threshold for a default swap file can exceed the number of disk pages
allocated. The threshold is relative to the default maximum size of the file instead
of to the bytes currently allocated. For example, the threshold for default swap files
for systems running H-series RUVs is 85% of 512 megabytes, or 435.2
megabytes, even if fewer than 512 megabytes are currently allocated for the
default swap file.
KMS Files and New Systems
New systems do not have any swap files configured. They use only the default swap
files. To load a new system, $SYSTEM must have enough unused disk space:
•
For systems running H-series RVUs, you need at least 512 megabytes for the
system-load processor and an additional 512 megabytes for each additional
processor.
•
For systems running G06.27 and later G-series RVUs, you need at least 256
megabytes for the system-load processor and an additional 256 megabytes for
each additional processor you want to load.
•
For systems running G06.26 and earlier G-series RVUs, you need at least 128
megabytes for the system-load processor and an additional 128 megabytes for
each additional processor you want to load.
Because default swap files start with an initial allocation and grow as needed, the
allocated file size might not be the maximum permitted file size. Example 1-2
on
page 1-11 shows a system that only has default swap files and is running an H-series
RVU.
Note. Each processor requires more swap space than provided by the default swap files.
After the default swap files have been opened, increase the size of the swap files or
configure more swap files for each processor. For information about how much swap
space to allocate, refer to Amount of Swap Space to Allocate
on page 2-2.