On Oct 20, 2015, at 6:37 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > > > I am suggesting that a user wishes to NOT USE a specific port at all. > In other words, I want to "obstruct" all of the API paths that might reach > that port. > However, they do want to use some other port of the same type - which means > they cannot disable entire BTLs or MTLs. > > Unless I am missing something, they need to consider each possible API path > through OMPI and pass a corresponding MCA param, such as > btl_openib_if_exclude, to prevent that path from selecting the port in > question.
Yeah, this is currently correct. > The problem is that the user may not know all the API paths that need to have > a corresponding exclude. Agreed -- now I see your connection to the "how do I disable MXM?" question. > This is, in some ways, similar to the initial problem of how to disable all > uses of mxm - it currently requires knowledge of all API paths that "might > get you there". Gotcha. > I am now seeing my concern turn in another direction, because a quick grep > for "_exclude" in the OMPI 1.10.1 source turned up matches in only the openbl > and usnic BLTs, and in oob_tcp. > Is it really the case that an end user cannot instruct mxm, psm, psm2, > portals4 or ofi not to use a specific IB port via mpirun? Strike "IB" from your question -- yes, I guess we don't have uniform include/exclude support across all the BTLs and MTLs. I agree: that does seem a bit problematic. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
