-
Notifications
You must be signed in to change notification settings - Fork 4
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
Custom intrinsic scopes #72
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have predefined intrinsic scopes such as
QV_SCOPE_USER
andQV_SCOPE_PROCESS
. It would be helpful to allow users to define intrinsic scopes that external libraries can use for computing.Let's say I have an application that calls into a QV-enabled MPI library and this application wants the MPI library to use specific cores for doing MPI progress. Since the app cannot change the MPI API, passing these resources as a scope has to be done implicitly. The app could create an intrinsic scope via:
The MPI library would then use the resources associated with
QV_SCOPE_UTILITY
to launch its progress threads:Among other things, this may involve changing the type of
iscope
inAlternatively, we can allow users to custom-define a specific intrinsic scope, say
QV_SCOPE_UTILITY
, rather than allow them to create custom intrinsic scopes in general. This would work too and, perhaps, would make the implementation easier 😃In this case the following call would work, but it would only be supported for
QV_SCOPE_UTILITY
(and other specific names if we decide to extend this capability):Note that
QV_SCOPE_UTILITY
would be an enum, not a string, since QV would control the names of all the intrinsic scopes 😄The text was updated successfully, but these errors were encountered: