I'm sorry; I really wasn't paying attention to my email the week of SC, and then I was on vacation for the Thanksgiving holiday. :-\
More below. On Nov 20, 2013, at 4:13 PM, Compres <compr...@in.tum.de> wrote: > I was at the birds of a feather and wanted to talk to the Open MPI > developers, but unfortunately had to leave early. In particular, I would > like to discuss about your implementation of the MPI tools interface and > possibly contribute to it later on. Sorry we missed you. What did you want to discuss? We actually have a full implementation of the MPI_T interface -- meaning that we have all the infrastructure in place for MPI_T control and performance variables. 1. The MPI_T control variables map directly to OMPI's MCA params, so we automatically expose oodles of cvars through MPI_T. They're all read-only after MPI_INIT, however -- many things are setup during MPI_INIT and it would be quite a Big Deal if they were to change. However, we pretty much *assumed* all cvars shouldn't change after INIT -- we didn't really audit to see if there were actually some cvars that could change after INIT. So there's work that could be done there (i.e., find cvars that could change after INIT, and/or evaluate the amount of work/change it would be to change some read-only cvars to be read-write, etc.). 2. The MPI_T performance variables are new. There's only a few created right now (e.g., in the Cisco usnic BTL). But the field is pretty wide open here -- the infrastructure is there, but we're really not exposing much information yet. There's lots that can be done here. What did you have in mind? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
