You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a single process supporting multiple libfabric clients (e.g., MPI and DAOS), this raises the question how to properly set libfabric environment variables. Specifically, one set of environment variables may only be applicable to one libfabric client (example: #10526)
Has anyone else ran into this problem? For CXI provider specific env vars, we do support setting some via fi_domain get/set opts. But, this seems like a more general problem where a libfabric-level solution would be ideal.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With a single process supporting multiple libfabric clients (e.g., MPI and DAOS), this raises the question how to properly set libfabric environment variables. Specifically, one set of environment variables may only be applicable to one libfabric client (example: #10526)
Has anyone else ran into this problem? For CXI provider specific env vars, we do support setting some via fi_domain get/set opts. But, this seems like a more general problem where a libfabric-level solution would be ideal.
Beta Was this translation helpful? Give feedback.
All reactions