On Mar 16, 2016, at 12:52 PM, dpchoudh . <dpcho...@gmail.com> wrote: > > Sorry about asking too many 101 level question, but here is another one: > > I have a BTL layer code, called 'lf' that is ready for unit testing; it > compiles with the OMPI tool chain (by doing a ./configure; make from the top > level directory) and have the basic data transport calls implemented. > > How do I 'hook up' the BTL to the OMPI call chain? > > If I do the following: > mpirin -np 2 --hostfile ~/hostfile -mca btl lf,self ./NPmpi > > it fails to run and the gist of the failure is that it does not even attempt > connecting with the 'lf' BTL (the error says: 'BTLs attempted: self')
It usually means one of two things: 1. That your BTL failed to dlopen/load. Although you should typically see a warning/error about the component failing to load when that happens, so it should be obvious. More generally, you should be able to "ompi_info | grep btl" and see your lf BTL. If so, then it's probably loading properly in your MPI processes, too. 2. That you BTL elected not to run. E.g., it returned a failure from the component open or init. Double check what you're returning from these functions. Pro tip: you can use opal_output(0, "your message") to output process/PID-tagged output from MPI processes for debugging purposes. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
