Hi Jeff, Thank you for your advice. I will contact the author for some suggestions. I also notice I may port this old version library to new openmpi 3.0. I will work on this soon. Thank you.
Kaiming Ouyang, Research Assistant. Department of Computer Science and Engineering University of California, Riverside 900 University Avenue, Riverside, CA 92521 On Wed, Mar 21, 2018 at 5:24 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com > wrote: > You might want to take that library author's advice from their README: > > ----- > The source code herein was used as the basis of Rountree ICS 2009. It > was my first nontrivial MPI tool and was never intended to be released > to the wider world. I beleive it was tied rather tightly to a subset > of a (now) old MPI implementation. I expect a nontrivial amount of > work would have to be done to get this to compile and run again, and > that effort would probably be better served starting from scratch > (using Todd Gamblin's wrap.py PMPI shim generator, for example). > ----- > > > > On Mar 21, 2018, at 2:23 AM, John Hearns via users < > users@lists.open-mpi.org> wrote: > > > > Kaiming, good luck with your project. I think you should contact Barry > Rountree directly. you will probably get good advice! > > > > It is worth saying that with Turboboost there is variation between each > individual CPU die, even within the same SKU. > > What Turboboost does is to set a thermal envelope, and the CPU core(s) > ramp up in frequency till the thermal limit is reached. > > So each CPU die is slightly different (*) > > Indeed in my last job we had a benchmarking exercise where the > instruction was to explicitly turn off Turboboost. > > > > > > (*) As I work at ASML I really should understand this better... I really > should. > > > > > > > > > > > > > > On 20 March 2018 at 19:34, Kaiming Ouyang <kouya...@ucr.edu> wrote: > > Hi John, > > Thank you for your advice. But this is only related to its > functionality, and right now my problem is it cannot compile with new > version openmpi. > > The reason may come from its patch file since it needs to intercept MPI > calls to profile some data. New version openmpi may change its framework so > that this old software does not fit it anymore. > > > > > > Kaiming Ouyang, Research Assistant. > > Department of Computer Science and Engineering > > University of California, Riverside > > 900 University Avenue, Riverside, CA 92521 > > > > > > On Tue, Mar 20, 2018 at 10:46 AM, John Hearns via users < > users@lists.open-mpi.org> wrote: > > "It does not handle more recent improvements such as Intel's turbo > > mode and the processor performance inhomogeneity that comes with it." > > I guess it is easy enough to disable Turbo mode in the BIOS though. > > > > > > > > On 20 March 2018 at 17:48, Kaiming Ouyang <kouya...@ucr.edu> wrote: > > I think the problem it has is it only deal with the old framework > because it will intercept MPI calls and do some profiling. Here is the > library: > > https://github.com/LLNL/Adagio > > > > I checked the openmpi changelog. From openmpi 1.3, it began to switch to > a new framework, and openmpi 1.4+ has different one too. This library only > works under openmpi 1.2. > > Thank you for your advise, I will try it. My current problem is this > library seems to try to patch mpi.h file, but it fails during the patching > process for new version openmpi. I don't know the reason yet, and will > check it soon. Thank you. > > > > Kaiming Ouyang, Research Assistant. > > Department of Computer Science and Engineering > > University of California, Riverside > > 900 University Avenue, Riverside, CA 92521 > > > > > > On Tue, Mar 20, 2018 at 4:35 AM, Jeff Squyres (jsquyres) < > jsquy...@cisco.com> wrote: > > On Mar 19, 2018, at 11:32 PM, Kaiming Ouyang <kouya...@ucr.edu> wrote: > > > > > > Thank you. > > > I am using newest version HPL. > > > I forgot to say I can run HPL with openmpi-3.0 under infiniband. The > reason I want to use old version is I need to compile a library that only > supports old version openmpi, so I am trying to do this tricky job. > > > > Gotcha. > > > > Is there something in particular about the old library that requires > Open MPI v1.2.x? > > > > More specifically: is there a particular error you get when you try to > use Open MPI v3.0.0 with that library? > > > > I ask because if the app supports the MPI API in Open MPI v1.2.9, then > it also supports the MPI API in Open MPI v3.0.0. We *have* changed lots of > other things under the covers in that time, such as: > > > > - how those MPI API's are implemented > > - mpirun (and friends) command line parameters > > - MCA parameters > > - compilation flags > > > > But many of those things might actually be mostly -- if not entirely -- > hidden from a library that uses MPI. > > > > My point: it may be easier to get your library to use a newer version of > Open MPI than you think. For example, if the library has some hard-coded > flags in their configure/Makefile to build with Open MPI, just replace > those flags with `mpicc --showme:BLAH` variants (see `mpicc --showme:help` > for a full listing). This will have Open MPI tell you exactly what flags > it needs to compile, link, etc. > > > > -- > > Jeff Squyres > > jsquy...@cisco.com > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/users > > > -- > Jeff Squyres > jsquy...@cisco.com > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
