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
In order to make the use of UnifyCR more seamless, it is desirable to eliminate the need for client applications to directly call unifycr_mount() and unifycr_unmount(). Thus, we would like to call these functions as part of the client library's static initialization and finalization. This issue is to document the roadblocks to doing such static setup/teardown.
Initialization roadblocks
MPI is used extensively during unifycr_mount(), but an application will not call MPI_Init() until after the library is initialized. Similarly, the MPI rank space is used as the UnifyCR global rank space, and the local rank and size of MPI_COMM_WORLD are passed as arguments to unifycr_mount().
Finalization roadblocks
No problems identified yet.
The text was updated successfully, but these errors were encountered:
Description
In order to make the use of UnifyCR more seamless, it is desirable to eliminate the need for client applications to directly call
unifycr_mount()
andunifycr_unmount()
. Thus, we would like to call these functions as part of the client library's static initialization and finalization. This issue is to document the roadblocks to doing such static setup/teardown.Initialization roadblocks
unifycr_mount()
, but an application will not callMPI_Init()
until after the library is initialized. Similarly, the MPI rank space is used as the UnifyCR global rank space, and the local rank and size ofMPI_COMM_WORLD
are passed as arguments tounifycr_mount()
.Finalization roadblocks
The text was updated successfully, but these errors were encountered: