I tend to agree with Chris. Changing the behavior of the 1.3 in the
middle of the stable release cycle, will be very confusing for our
users. Moreover, as Ralph pointed out, everything in Open MPI is
configurable so if we advertise this feature in the Changelog, the
institutions where the nodes are not shared can easily amend their
configuration files to take advantage of it. In particular, for Sun,
if we push this feature in the 1.3.4 release, they can ship their
version (derived from the 1.3.4) with the MCA parameter set to bind-to-
We can bring this topic in the spotlight for the next cycle (1.4/1.5).
On Aug 16, 2009, at 20:42 , Chris Samuel wrote:
> ----- "Ralph Castain" <rhc_at_[hidden]> wrote:
>> Hi Chris
> Hiya Ralph,
>> 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
> I think this is too big a change in the default behaviour
> for a stable release, it'll cause a lot of people pain for
> no readily apparent reason.
> I also believe that if those sites with multiple MPI jobs
> on nodes are indeed in the majority then it makes more sense
> to keep the default behaviour and have those who need this
> functionality enable it on their installs.
> Thoughts ?
> 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