hkaiser 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/ | GSoD: https://developers.google.com/season-of-docs/
weilewei has quit [Remote host closed the connection]
K-ballo has quit [Quit: K-ballo]
<jaafar> Can someone point me to a concise summary of the launch policies?
<jaafar> I can see they make a performance difference but I don't know why
<jaafar> and I have some other confusions
<jaafar> For example: the fork policy says it enables "continuation stealing" but I can't find any explanation of what this is
<jaafar> And on the surface, the async policy lets a task run concurrently to the launcher
<jaafar> But AFAICT that is true of the sync policy as well!
<jaafar> So in summary: scratching my head :)
<hkaiser> jaafar: sorry, let's talk tomorrow - I'll explain everything
hkaiser has quit [Ping timeout: 250 seconds]
nikunj has quit [Quit: Bye]
nikunj has joined #ste||ar
<jaafar> yay sounds good
nikunj has quit [Remote host closed the connection]
nikunj has joined #ste||ar
Yorlik has joined #ste||ar
nikunj has quit [Ping timeout: 240 seconds]
nikunj has joined #ste||ar
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
hkaiser has quit [Ping timeout: 264 seconds]
aserio has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo has joined #ste||ar
K-ballo has quit [Remote host closed the connection]
K-ballo has joined #ste||ar
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
weilewei has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 240 seconds]
K-ballo1 is now known as K-ballo
diehlpk has joined #ste||ar
hkaiser has joined #ste||ar
diehlpk has quit [Ping timeout: 250 seconds]
<diehlpk_work> simbergm, aserio Can you fill in the Season of Doc mentor survey?
aserio has quit [Ping timeout: 250 seconds]
aserio has joined #ste||ar
aserio1 has joined #ste||ar
aserio has quit [Ping timeout: 250 seconds]
aserio1 is now known as aserio
aserio has quit [Quit: aserio]
aserio has joined #ste||ar
<heller> hkaiser: BTW, you were right, a parcelport might indeed be the least intrusive work
<heller> On both sides
<hkaiser> heller: heh
<heller> This is very exciting
<heller> The best thing, imho, I didn't play the performance card
<heller> But the maintainability/usability card
aserio has quit [Ping timeout: 245 seconds]
hkaiser has quit [Ping timeout: 264 seconds]
weilewei has quit [Remote host closed the connection]
hkaiser has joined #ste||ar
<hkaiser> heller: right - good move
aserio has joined #ste||ar
aserio has quit [Client Quit]
nikunj has quit [Remote host closed the connection]
jbjnr has quit [Read error: Connection reset by peer]
nikunj has joined #ste||ar
<jaafar> hkaiser: if you have a sec to send me some launch policy info I would be grateful
<jaafar> just a pointer is fine
* jaafar couldn't find anything detailed enough
<hkaiser> jaafar: launch::async should be clear
<hkaiser> it schedules a new thread and goes on with the current one
<hkaiser> launch::fork schedules a new thread and continues with the new thread, rescheduling the current one for later
<hkaiser> launch::sync should be synchronous, except for remote operations, where its equivalent to async().get()
<jaafar> hkaiser: it seemed to me that sync actually launched asynchronously as well but maybe I'm confused :)
<jaafar> at least it seems to be non-blocking, am I wrong?
<hkaiser> uhh, shouldn't be :/
<hkaiser> sync should be - well - sync
<hkaiser> gotta run again, bbl
<hkaiser> there is also hpx::sync btw, it's equivalent to hpx::async(launch::sync, ...) with the caveat that if the launched task returns a future, no additional future is created
<hkaiser> I'll have a look
<hkaiser> gtg
<jaafar> OK later
Coldblackice has joined #ste||ar
hkaiser has quit [Ping timeout: 245 seconds]