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 short, I would like to be able to run two tasks with each an own thread in my code in which both tasks can use @tturbo on nested loops. One of the tasks might trigger MPI communication, and I would like the other task to continue computation. As @chriselrod suggested in the Discourse discussion, a spawn is missing in Polyester. I would like to give it a try (I will need some time to figure out the code and its interactions with PolyesterWeave and ThreadingUtilities). What would be necessary for my goal is to give priority to threads. I thought of doing this in two steps. First, to solve the issue raised in the discourse discussion, and then the priority issue. It would be great to get some initial hints on in which file to implement the spawn, following up on the hints given in de Discourse post.
The text was updated successfully, but these errors were encountered:
I opened an issue here following the discourse discussion: https://discourse.julialang.org/t/how-to-control-threads-in-combination-of-loopvectorization-and-spawn/75466
In short, I would like to be able to run two tasks with each an own thread in my code in which both tasks can use
@tturbo
on nested loops. One of the tasks might trigger MPI communication, and I would like the other task to continue computation. As @chriselrod suggested in the Discourse discussion, a spawn is missing in Polyester. I would like to give it a try (I will need some time to figure out the code and its interactions with PolyesterWeave and ThreadingUtilities). What would be necessary for my goal is to give priority to threads. I thought of doing this in two steps. First, to solve the issue raised in the discourse discussion, and then the priority issue. It would be great to get some initial hints on in which file to implement the spawn, following up on the hints given in de Discourse post.The text was updated successfully, but these errors were encountered: