John, The 1st case. All processors of a type in summary have specified share value. So, You may have 1 PU, with specified share (let's, it will CP, the share is 100), you may define another CPU (via CP DEF CPU 1 TYPE CP command), each CPU will have 50 points of relative share then, and the sum remains 100. We make another CPU with type CP plus -- one processor will work with share 34, and two others -- with share 33.
Meanwhile, if you try to define a CPU with other type (let's, IFL) and your LPAR has an IFL processor online, your userid has CPUAFFINITY=ON, then all three CP processors remain own share values (34/33/33). The SET CPUAFFINITY OFF command says to VM CP to dispatch all your virtual processors as CP, the share will: 25/25/25/25. Sametime, if your LPAR does not have an IFL processor online, your new just defined virtual IFL processor will dispatch as CP too (even CPUAFFINITY=ON), the status will as SUPPRESSED. As result -- the same 25/25/25/25 for our example. Is clear the picture? 2011/4/11 John Hanley <jhan...@courts.state.va.us> > When setting an absolute share value for a virtual machine with multi > virtual CPU'S and CPUAFFINITY=ON, > is the absolute value divided between the CPU'S or does each CPU get the > set value? > The doc seem a little vague on this for CPUAFFINITY=ON or OFF. > Thanks. > -- WBR, =Maxim Bochagov IBM Russia, PTK development team
