The branch will be merged once we know make check succeeds on arm64 with —disable-builtin-atomics. Just waiting on that testing.
-Nathan > On Jun 1, 2016, at 10:22 PM, Sreenidhi Bharathkar Ramesh > <sreenidhi-bharathkar.ram...@broadcom.com> wrote: > > Thank you for the response. > > Nathan, > Sure, we will try out your branch and let you know. Any idea when it is > likely to be pulled into master ? > I presume that our changes, if any, will need to be on top of these changes. > > Jeff, > > A few clarifications please: > > > a) run MTT regularly and submit the results to the community database > > Is MTT required along with initial proposed branch ? Also, what regularity > of MTT is required after submission ? > > I apologize if these questions sound basic. We are just getting started, > hence asking. > > Thanks! > - Sreenidhi. > > On Tue, May 31, 2016 at 7:33 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > Let me address the questions Nathan didn't: > > - testing: if you're adding support for a platform that we don't test, it's > likely that the code will grow stale and eventually be removed. The best way > to make sure a platform stays supported is to a) run MTT regularly and submit > the results to the community database, and b) make sure that there are tests > that are exercising the code paths you're adding for your platform. > > - submissions are added to release branches on a rolling basis. You're too > late for the 2.0.x series, but the door is open for the v2.1.x series (and > beyond, of course). > > > > > On May 30, 2016, at 11:15 AM, Nathan Hjelm <hje...@me.com> wrote: > > > > I should clarify. The PR adds support for ARM64 atomics and CMA when the > > linux headers are not installed. It does not update the timer code and > > still needs some testing. > > > > -Nathan > > > >> On May 30, 2016, at 8:37 AM, Nathan Hjelm <hje...@me.com> wrote: > >> > >> We already have a PR open to add ARM64 support. Please test > >> https://github.com/open-mpi/ompi/pull/1634 and let me know if it works for > >> you. Additional contributions are greatly appreciated! > >> > >> -Nathan > >> > >> On May 30, 2016, at 4:32 AM, Sreenidhi Bharathkar Ramesh > >> <sreenidhi-bharathkar.ram...@broadcom.com> wrote: > >> > >>> Hello, > >>> > >>> We may be in a position to contribute to Open MPI, initially by adding > >>> ARM64 support. Specifically, atomics and Timer support. > >>> > >>> I have already gone through: > >>> https://www.open-mpi.org/community/contribute/ > >>> https://www.open-mpi.org/faq/?category=contributing > >>> > >>> Please let me know: > >>> > >>> 1. baseline for the patch > >>> 2. test logs and results that are expected > >>> 3. any cutoffs from release timeline perspective > >>> > >>> Thanks, > >>> - Sreenidhi. > >>> _______________________________________________ > >>> devel mailing list > >>> de...@open-mpi.org > >>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > >>> Link to this post: > >>> http://www.open-mpi.org/community/lists/devel/2016/05/19048.php > > > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > > http://www.open-mpi.org/community/lists/devel/2016/05/19050.php > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/05/19051.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/06/19057.php
signature.asc
Description: Message signed with OpenPGP using GPGMail
