Re: [zones-discuss] psets for zones
Are you still trouble with which site you can trust to buy [url=http://www.gameim.com/product/RuneScape_II_gold.html]RS Gold[/url] safely, I'll introduce one for you, I have bought [url=http://www.gameim.com/product/RuneScape_II_gold.html]Runescape Gold[/url] many times from here, if you want to buy [url=http://www.gameim.com/product/RuneScape_II_gold.html]RS Money[/url], trust me!!try!! -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] psets for zones
Also, using method (2), you have told the Solaris kernel that it can move CPUs out of pset1 if another pset needs them. --JeffV On Thu, Mar 10, 2011 at 2:35 PM, Christian Meier wrote: > Hello, > > also have a look at the pset.load value. As long as the load is higher > than the pset.max the pset.size will not be under 5 > expect you have an other pool with a higher importance. > As soon as the load is coming under 5 the cpu's will be assigned to an > other pool or pool_default > >>> pset pset1 >>> int pset.sys_id 1 >>> boolean pset.default false >>> uint pset.min 1 >>> uint pset.max 5 >>> string pset.units population >>> uint pset.load 10 >>> uint pset.size 5 >>> string pset.comment > > Regards > Christian > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org > -- --JeffV ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] psets for zones
Hello, also have a look at the pset.load value. As long as the load is higher than the pset.max the pset.size will not be under 5 expect you have an other pool with a higher importance. As soon as the load is coming under 5 the cpu's will be assigned to an other pool or pool_default >> pset pset1 >> int pset.sys_id 1 >> boolean pset.default false >> uint pset.min 1 >> uint pset.max 5 >> string pset.units population >> uint pset.load 10 >> uint pset.size 5 >> string pset.comment Regards Christian ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] psets for zones
When "pooladm -c" is done to commit the configuration, it will try and satisfy the min/max constraints of all psets. In your case, there are plenty of cpus, so pset1 gets 5 cpus. If you had more psets configured, there might not be enough cpus to give pset1 5 cpus. If the pset.min off all psets cannot be satisfied, "pooladm -c" will fail. -Steve L. On 03/10/11 09:54 AM, Ketan wrote: I configured the the pset1 with 2 different ways 1. poolcfg -c 'create pset pset1 (uint pset.min = 5; uint pset.max = 5)' pset pset1 int pset.sys_id 1 boolean pset.default false uint pset.min 5 uint pset.max 5 string pset.units population uint pset.load 7 uint pset.size 5 string pset.comment * * 2. 1. poolcfg -c 'create pset pset1 (uint pset.min = 1; uint pset.max = 5)' pset pset1 int pset.sys_id 1 boolean pset.default false uint pset.min 1 uint pset.max 5 string pset.units population uint pset.load 10 uint pset.size 5 string pset.comment whats the difference in both of them .. the only difference i can see is uint.min=5 and uint.min=1 but the pset.size is 5 for both the cases so is it just a different way of notation of some other difference too ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] psets for zones
I configured the the pset1 with 2 different ways 1. poolcfg -c 'create pset pset1 (uint pset.min = 5; uint pset.max = 5)' pset pset1 int pset.sys_id 1 boolean pset.default false uint pset.min 5 uint pset.max 5 string pset.units population uint pset.load 7 uint pset.size 5 string pset.comment * * 2. 1. poolcfg -c 'create pset pset1 (uint pset.min = 1; uint pset.max = 5)' pset pset1 int pset.sys_id 1 boolean pset.default false uint pset.min 1 uint pset.max 5 string pset.units population uint pset.load 10 uint pset.size 5 string pset.comment whats the difference in both of them .. the only difference i can see is uint.min=5 and uint.min=1 but the pset.size is 5 for both the cases so is it just a different way of notation of some other difference too -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org