> I tried, but for some threads, I got surprising results: > > > ./plgrp -a all 27215 > PID/LWPID HOME AFFINITY > 27215/1 2 5/strong,0-4,6-24/none > > If the home lgroup is defined as the lgroup with the strongest > affinity, isn't the output above somewhat contradictory? > > > ./plgrp -F -H 5 27215 > PID/LWPID HOME > 27215/1 2 => 2 > > This thread seems to be resistant to plgrp's attempts to assign a new > home lgroup (option -H) to it. > > This is a test program. For some other threads, I was able to freely > rehome them to any lgroup in the range 1..8 (the leaf lgroups). Has > anyone some further suggestions on what could prevent reassigning the > home lgroup?
It's possible that processor sets or bindings are taking precedence over the affinity you've chosen for this PID. Each of these mechanisms restricts what CPUs a process may use. In that case, the home lgrp gets constrained to one that has resources within your binding. The the following commands would tell you if your process is bound, or in a processor set. $ pbind -q 27215 and $ psrset -q 27215 Hope this helps. -j _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
