Re: [OMPI devel] [OMPI users] Backward Compatibility of MPI Java Binding
> Yes -- IIRC, the Java interface isn't really dependent upon anything specific > in the back-end C implementation of Open MPI. So I'm guessing/assuming that > if you can build it, it should work against the 1.6 OMPI C engine just fine. Sounds good :-) I'm going to try to build it anyway, and let you know if stucked. > Is MPI-for-Java of interest to you? I ask because Ralph and I have been > trying to figure out how to get the cycles to do more with the Java interface > (e.g., make it more like a 1:1 set of bindings). Is this something you'd be > willing to work on / contribute, perchance? Yes. This is because one of our roles is enabling Java applications to run on top of the K computer (Fujitsu), which prevents user processes from TCP/IP communications directly. It only allows communications via customized openmpi (scheduler) between inter node communications. BTW, I don't fully understand what a 1:1 set of bindings mean. I believe that the interfaces defined in mpiJava was carefully designed to match the MPI spec, and then should be a 1:1 set of bindings. Otherwise, I'm willing to contribute something to make it better ;-) Thanks, --yoshiki On 2013/01/10, at 20:45, Jeff Squyres (jsquyres) wrote: > On Jan 9, 2013, at 10:30 PM, Yoshiki SATO > wrote: > >> The 1.7's Java implementation under ompi/mpi/java seem to be able to build >> up independently. Do you think we can build just them and run it (via >> prunjava?) with our custom OpenMPI build based on 1.6? > > > Yes -- IIRC, the Java interface isn't really dependent upon anything specific > in the back-end C implementation of Open MPI. So I'm guessing/assuming that > if you can build it, it should work against the 1.6 OMPI C engine just fine. > > Is MPI-for-Java of interest to you? I ask because Ralph and I have been > trying to figure out how to get the cycles to do more with the Java interface > (e.g., make it more like a 1:1 set of bindings). Is this something you'd be > willing to work on / contribute, perchance? > > -- > 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 > http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] [OMPI users] Backward Compatibility of MPI Java Binding
On Jan 9, 2013, at 10:30 PM, Yoshiki SATO wrote: > The 1.7's Java implementation under ompi/mpi/java seem to be able to build up > independently. Do you think we can build just them and run it (via > prunjava?) with our custom OpenMPI build based on 1.6? Yes -- IIRC, the Java interface isn't really dependent upon anything specific in the back-end C implementation of Open MPI. So I'm guessing/assuming that if you can build it, it should work against the 1.6 OMPI C engine just fine. Is MPI-for-Java of interest to you? I ask because Ralph and I have been trying to figure out how to get the cycles to do more with the Java interface (e.g., make it more like a 1:1 set of bindings). Is this something you'd be willing to work on / contribute, perchance? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] [OMPI users] Backward Compatibility of MPI Java Binding
Thanks for your suggestion. I resend my question here. > it's just something that happened over time (our methodology is that we > branch away from the main development trunk and then only selectively apply > patches from the main trunk to the release branch over time). The 1.7's Java implementation under ompi/mpi/java seem to be able to build up independently. Do you think we can build just them and run it (via prunjava?) with our custom OpenMPI build based on 1.6? Regards, --yoshiki On 2013/01/10, at 2:38, Jeff Squyres (jsquyres) wrote: > On Jan 8, 2013, at 3:23 AM, Yoshiki SATO wrote: > >> Could you let me know the details of that? > > We don't have a technical writeup of what changed in the configure/build > system between the two; it's just something that happened over time (our > methodology is that we branch away from the main development trunk and then > only selectively apply patches from the main trunk to the release branch over > time). > > The differences between the configure/build system between v1.6 and the SVN > trunk are now fairly large, for example: > > - trunk uses autogen.pl; v1.6 uses autogen.sh > - trunk uses many more _ prefixes (but not all) to m4 macros; v1.6 > doesn't > - trunk has most .m4 files in config/; v1.6 distributes them around config/ > and /config/ directories > - trunk has different requirements for each > - many global shell variable names have changed between trunk and v1.6 > - Fortran support, for example, was completely revamped on the trunk, and has > very, very different .m4 tests than v1.6 > > I think the subsystems you'll have to update to port the Java interface to > the v1.6 branch include (this is more-or-less off the top of my head; it is > likely not all-inclusive): > > - update configure.ac > - port ompi_setup_java.m4 and orte_setup_java.m4 > - port ompi/mpi/java > - update ompi/Makefile.am > > If you endeavor to do this and need some help, please ask questions over on > the devel list (not the user's list). > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >> Hi, >> >> The MPI Java binding being developed on the 1.7 pre-release. Is it possible >> to merge it with 1.5 or 1.6 releases? >> Our OpenMPI installation has large modifications to adopt specific network >> channels. Thus, it would be happy to work the MPI Java binding even with >> old OpenMPI binaries/libraries. >> >> Thanks a lot for any comment in advance. >> >> Regards, >> --yoshiki
