Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove --enable-heterogenous configury option #2802

Closed
hppritcha opened this issue Jan 24, 2017 · 8 comments
Closed

remove --enable-heterogenous configury option #2802

hppritcha opened this issue Jan 24, 2017 · 8 comments
Assignees
Milestone

Comments

@hppritcha
Copy link
Member

Mixed big endian/little endian no longer works in Open MPI and there are no plans currently to fix it. To avoid user confusion, remove the configure --enable-heterogenous option. Related to issue #639.

Rather than just removing entirely from the configury, it would be better to have configure print out an error message if this option is attempted and abort.

@ggouaillardet
Copy link
Contributor

the test provided in #168 runs fine with master + a few patches of mine.
i am happy to maintain the --enable-heterogeneous option, maybe v2.1.0 is a reasonable target so i can test and backport what is needed

there was a previous RFC to get rid of heterogeneous support at https://www.open-mpi.org/community/lists/devel/2014/04/14584.php
and we did not decide to get rid of that.

@jsquyres @bosilca any thoughts ?

@ggouaillardet
Copy link
Contributor

fwiw, this was mentionned (and in a negative way) in that post that got some audience at that time
http://gentryx.de/news_the_troubling_state_of_MPI.html

@nrgraham23
Copy link
Contributor

nrgraham23 commented Jan 25, 2017

@jsquyres Do you want me to remove the dead code disabling this option will produce as well? Or I can leave it in incase we decided to support this option again in the future.

I have a fix ready if you just want the option disabled.

@hppritcha
Copy link
Member Author

Maintaining means testing. If we are going to maintain I'd like to see either a MTT or CI test of the hetero feature.

@ggouaillardet
Copy link
Contributor

the first step is to configure with --enable-heterogeneous and run MTT on a homogeneous cluster.
this is currently done by @jsquyres , see https://mtt.open-mpi.org/index.php?do_redir=2387

the second step is to configure with --enable-heterogeneous on at least two heterogeneous arch, and tests/run MTT on an heterogeneous cluster.
i believe @siegmargross run some basic tests on a regular basis (and we do get some reports when issues occur). i also run the ibm test suite on an heterogeneous cluster. the process is manual yet
(i do not think that could be fully automated in MTT, at least today) and i will see how i can upload the test results to MTT

@rhc54
Copy link
Contributor

rhc54 commented Jan 31, 2017

@ggouaillardet We talked about this on the telecon this morning, and bottom line is that we will apply our usual policy here: if someone is willing to maintain and test this feature, then no problem leaving it in the code. This probably applies sooner to v2.1 than v2.0.3, but if you can update the support and at least post on the PR your MTT results, then we are content to leave this alive.

@Kawashima-Azumi
Copy link

Kawashima-Azumi commented Feb 5, 2017

At present I don't care about BE/LE support but one scenario of my use cases is to make remote calls to x86_64 servers (LE) with high electric power consumption from a low power 32-bit system (LE). Will this be affected if heterogeneous support is removed?

@jsquyres
Copy link
Member

jsquyres commented Feb 8, 2017

I think this issue is now moot, per #2802 (comment) and #2940.

@jsquyres jsquyres closed this as completed Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants