Configuring and Migrating Memory on vPars

To add 1 GB as base and 512 MB as floating CLM from cell 0 to vpar1 and 512 MB as base and

512 MB as floating CLM from cell 1 to vpar2, we would do the following:

# vparmodify –p vpar1 –a cell:0:mem::1024 –a cell:0:mem::512:f

# vparmodify –p vpar2 –a cell:1:mem::512 –a cell:1:mem::512:f

Assuming both vpar1 and vpar2 are live, to remove 512 MB of floating ILM from vpar2 and add it to

vpar1 as base ILM, we would do the following:

# vparmodify –p vpar2 –d mem::512:f

# vparmodify –p vpar1 –a mem::512

To remove 512 MB of base ILM from vpar1 and add it to vpar2 as floating ILM, we would shut down

vpar1 and once it is down issue the following commands to transfer memory from vpar1 to vpar2 and

then boot vpar1 back up:

# vparmodify –p vpar1 –d mem::512

# vparmodify –p vpar2 –a mem::512:f

Figure 2 below is an extension of Figure 1 and shows the memory distribution for the above example

with base and floating ILM and CLM when both vpar1 and vpar2 are live. At the end of the last

operation, vpar1 contains 512 MB base ILM, 1024 MB floating ILM, 1024 MB base CLM from cell 0

and 512 MB floating CLM from cell 0. vpar2 contains 1024 MB base ILM, 512 MB floating ILM,

512 MB base CLM from cell 1 and 512 MB floating CLM from cell 1. As will be explained later, the

vPar monitor tries to allocate base memory below the floating memory within each locality when the

partition is booted.

Figure 2 Base and Floating Memory Partitioning

Base and Floating Memory Guidelines

The following provides some guidelines on how to use base and floating memory in a vPars system:

• The system administrator is encouraged to configure enough base memory during partition boot

to achieve the required baseline application performance taking into consideration the

following two constraints:

Ø The kernel has more flexibility in using base memory. The kernel restricts the use of

floating memory to contents that it can later relocate if it is selected for deletion. Hence,