hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo1 is now known as K-ballo
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo1 is now known as K-ballo
hkaiser has quit [Quit: Bye!]
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 260 seconds]
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo has joined #ste||ar
Yorlik_ is now known as Yorlik
RostamLog_ has joined #ste||ar
RostamLog has quit [Ping timeout: 248 seconds]
hkaiser has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo1 is now known as K-ballo
<pansysk75[m]>
hkaiser: we've mentioned that HPX by default creates as many system threads as there are cores, and pins each thread to a core
<pansysk75[m]>
Is the local-thread(the one that handles the sequential part of an HPX program) one of those threads?
<pansysk75[m]>
Because that would mean that any work scheduled on that local thread cannot progress until we allow the thread to block
<pansysk75[m]>
* hkaiser: we've mentioned that HPX by default creates as many system threads as there are cores, and pins each thread to a core.
<pansysk75[m]>
Is the local-thread(the one that handles the sequential part of an HPX program) one of those threads?
<pansysk75[m]>
In other words, if each thread has its own work-queue, the local thread has to be explicitly allowed to work on its work-queue, because it's not just a worker-thread but its also responsible for the main logic flow of the program
<pansysk75[m]>
I came across this asymmetry for my university assignment and I want to know if my thoughts are on the right track on this
<hkaiser>
pansysk75[m]: I'm not sure I understand
<hkaiser>
the thread that executes main() is put to sleep until the runtime exits
<hkaiser>
in HPX, that is
tufei has joined #ste||ar
diehlpk_work has joined #ste||ar
tufei_ has joined #ste||ar
tufei has quit [Ping timeout: 255 seconds]
diehlpk_work has quit [Remote host closed the connection]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 260 seconds]
K-ballo1 is now known as K-ballo
tufei_ has quit [Remote host closed the connection]