News for hackers. Stuff that matters.

A comment on Show HN: uThreads – Concurrent User Threads in C and C++. Parent comment

Re:Show HN: uThreads – Concurrent User Threads in C and C++ by rsp1984 on Monday November 07, 2016 @04:21PM (#12895241)
It sounds to me like what you'd need for ray tracing is a fork/join threading model with a master and several worker threads. OpenMP provides exactly that and is a widely supported standard. I'm curious: Why would you use anything else?
[ Parent | on HN ]
Re:Show HN: uThreads – Concurrent User Threads in C and C++ by CyberDildonics on Monday November 07, 2016 @05:07PM (#12895662)
Fork and join is one type of concurrency technique, but to think you wouldn't need anything else is silly. Non shared memory concurrency and pipelined concurrency are two more techniques that can be used.
[ Parent | on HN ]
Re:Show HN: uThreads – Concurrent User Threads in C and C++ by rsp1984 on Monday November 07, 2016 @05:49PM (#12895967)
I was stating this in the context of ray tracing. Why not just use OpenMP and be done with it?
[ Parent | on HN ]
Re:Show HN: uThreads – Concurrent User Threads in C and C++ by CyberDildonics on Wednesday November 09, 2016 @03:41PM (#12914419)
I answered that question. OpenMP fork-join concurrency can be useful for certain parts of a ray tracer depending on the overall architecture. It is far from the only way and can have many draw backs when it comes to overhead, synchronization and memory locality.
[ Parent | on HN ]