Configuring and Migrating Memory on vPars

15
to delete to optimize the deletion time. Hence, the granules selected for deletion need not be in any
specific order.
The following lists some of the side effects related to memory granule binding:
1. As evident from the example, due to the dynamism of memory binding, the ILM and CLM
address ranges associated with a partition change across reboots, deletes and adds. Hence,
the system administrator should not rely on a partition getting the same memory address
ranges.
2. If the system contains one or more memory granules with holes, the sum of the address ranges
during add, delete, or boot can vary slightly than the request. Suppose the granule size is 512
MB and the system contains four available granules: 512 MB, 480 MB, 400 MB and 420 MB.
The following details these variations:
a. If the partition that is being booted is allocated 1024 MB, it might get 512 MB and
480 MB granules, the sum of which is 992 MB instead of the1024 MB.
b. During the next boot, if the only available granules are 400 MB and 420 MB, then that
partition will get a total of 820 MB instead of the 992 MB it got during previous boot.
c. If the add request to a live partition is 512 MB and the available granules are 400 MB
and 420 MB, the partition might get the 420 MB granule.
d. If the delete request is 512 MB and the floating granule sizes in the live partition are
512 MB and 400 MB, the kernel might select 400 MB granule to delete if it can
evacuate it faster.
3. As explained in the previous chapter, on PA-RISC platforms, the memory granules below 2 GB
are used only for the partition’s kernel. Hence, during boot, the vPars monitor binds only the
required number of granules below 2 GB to load the partition’s kernel and the remaining are
picked from memory granules above 2 GB.