Using CUDA in a truly asynchronous event loop would be much easier if you could use it with select() or poll() system call (given a file descriptor), then just wait for some GPU completion event in the same way that you would wait for data from another thread or process. Now it has to be handled specifically, in a quite awkward way.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| CPU Spins while waiting for GPU to finish computation | 6 | 1538 | March 2, 2023 | |
| 100% CPU use while waiting for kernel | 7 | 4775 | July 10, 2008 | |
| CPU usage at 99% while kernel is running | 5 | 4538 | September 3, 2008 | |
| cudaMemcpy during kernel execution asynchronous kernel launch | 2 | 3141 | July 20, 2007 | |
| What happens to my CPU thread? | 1 | 1305 | August 19, 2009 | |
| cudaThreadSyncronize and cudaMemcpy | 2 | 2813 | February 11, 2008 | |
| A general question on Cuda Sync after kernal call | 3 | 428 | January 22, 2023 | |
| cudaMemcpy() Best approach when you need to call it many times? | 8 | 25279 | March 8, 2010 | |
| is kernel in stream 0 asynchronous? | 10 | 3817 | April 23, 2011 | |
| Synchronous cudaMemcpy locks GPU for other host threads/programs? | 1 | 892 | June 13, 2011 |