Hi Harshad,
> Sometime back we talked about an interface which could handle other
libraries calling cudaSetDevice simultaneously with PETSc. For example,
in our case 2 different instances of PETSc calling cudaSetDevice.
>Sure, but how will we actually share the device between libraries? What
>if the other library was not PETSc, but something else, and they also
>called cudaSetDevice, but with a different default mapping strategy?
>We need an interface that handles this case.
Do we already have any solution for this? If not, can we start looking
at this case?
I offered to provide a lazy initialization mechanism in order to be able
to deal with such cases - this is still on my todo-list. Due to other
obligations I couldn't find the time to implement this yet, but finally
things are getting better so that I can provide the changes soon.
Best regards,
Karli
