K-ballo changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
hkaiser has quit [Quit: bye]
<bering[m]> Why is it necessary to register OS threads in the HPX runtime?
<bering[m]> And is the comment in cuda_future.hpp related to the wrapper only or to the whole concept of thread registration?
<ms[m]> bering: partly to store some metadata about the the os thread, but mainly just to access the runtime pointer through a thread local variable
<ms[m]> but tbh I'm not sure it would need to be thread local (but I'm not 100% sure) and then registering wouldn'tbe required at least for the most common operations
<ms[m]> I suspect the todo refers to both, but I don't know
hkaiser has joined #ste||ar
Yorlik has joined #ste||ar
Yorlik has quit [Ping timeout: 250 seconds]
<gonidelis[m]> hkaiser can you ping me ?
<gonidelis[m]> on pm
Yorlik has joined #ste||ar
Yorlik has quit [Ping timeout: 258 seconds]