Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Static client initialization and finalization #134

Closed
MichaelBrim opened this issue Jun 21, 2018 · 3 comments
Closed

Static client initialization and finalization #134

MichaelBrim opened this issue Jun 21, 2018 · 3 comments
Assignees

Comments

@MichaelBrim
Copy link
Collaborator

MichaelBrim commented Jun 21, 2018

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() 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.
@MichaelBrim MichaelBrim self-assigned this Jun 21, 2018
@MichaelBrim
Copy link
Collaborator Author

In PR #288, Adam is working on using PMPI wrappers for MPI_Init and MPI_Finalize to call mount and unmount.

@MichaelBrim
Copy link
Collaborator Author

PR #298 added the PMPI wrapper method for mount/unmount

@adammoody
Copy link
Collaborator

Thanks @MichaelBrim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants