Hi Chris There would be a "-do-not-bind" option that will prevent us from binding processes to anything which should cover that situation.
My point was only that we would be changing the out-of-the-box behavior to the opposite of today's, so all those such as yourself would now have to add the -do-not-bind MCA param to your default MCA param file. Doable - but it -is- a significant change in our out-of-the-box behavior. On Sun, Aug 16, 2009 at 2:14 AM, Chris Samuel <csam...@vpac.org> wrote: > > ----- "Terry Dontje" <terry.don...@sun.com> wrote: > > > I just wanted to give everyone a heads up if they do not get bugs > > email. I just submitted a CMR to move over some new paffinity options > > from the trunk to the v1.3 branch. > > Ralphs comments imply that for those sites that share nodes > between jobs (such as ourselves, and most other sites that > I'm aware of in Australia) these changes will severely impact > performance. > > I think that would be a Very Bad Thing(tm). > > Can it be something that defaults to being configured out > for at least 1.3 please ? That way those few sites that > can take advantage can enable it whilst the rest of us > aren't impacted. > > cheers, > Chris > -- > Christopher Samuel - (03) 9925 4751 - Systems Manager > The Victorian Partnership for Advanced Computing > P.O. Box 201, Carlton South, VIC 3053, Australia > VPAC is a not-for-profit Registered Research Agency > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel >
