aserio 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/
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
<github>
[hpx] hkaiser force-pushed client_base_registration from 5741e55 to f38b014: https://git.io/vFJ7a
<github>
hpx/client_base_registration f38b014 Hartmut Kaiser: Making sure client_base instance that registered the component does not unregister it when being destructed
<jbjnr>
hkaiser: heller HLRS course. I'll clear it with my boss and get back to you
<heller>
Ok
<jbjnr>
Also - I am prepared to take over as GSoC admin for HPX if diehlpk_work does not want to continue doing it - he suggested at some point we do it together this yeat to ensure I know what to do.
<heller>
Sure
<hkaiser>
flag into your hand - go for it
<heller>
Me and Hartmut used to share the tasks, then Patrick took over
<heller>
Now it's your job :p
<jbjnr>
I like the T-Shirts and stickers :)
<heller>
I only got one sticker!
<hkaiser>
heller: I can give you the one I received
<hkaiser>
;)
<jbjnr>
very po this year indeed. and it was the same as last year's one
<jbjnr>
^poor
<heller>
If you're listed on the portal, you get the free stuff :p
<heller>
You don't have to do anything ;)
<jbjnr>
did you not mentor anyone?
<hkaiser>
shhh, don't tell him
<jbjnr>
rotten swizz
<github>
[hpx] biddisco force-pushed alloc_membind from 6524d7c to d9b91d1: https://git.io/vdnl9
<github>
hpx/alloc_membind e10c802 John Biddiscombe: Add hwloc alloc_membind support and nodeset bitmap type...
<github>
hpx/alloc_membind 513a4a4 John Biddiscombe: Add ostream operator for hwloc bitmap printout
<github>
hpx/alloc_membind d51fbe5 John Biddiscombe: Move hwloc_bitmap_ptr to threads namespace
<jbjnr>
dashboard looking much greener at the moment.
<jbjnr>
still not certain if they are the right ones, but code cimpilaes and runs ok now
<hkaiser>
jbjnr: looks good - I'd forward<>() the executor however if it's being passed in using a forwarding ref
<jbjnr>
good point. missed that.
david_pfander1 has joined #ste||ar
david_pfander1 has quit [Client Quit]
parsa has joined #ste||ar
hkaiser has quit [Quit: bye]
aserio has joined #ste||ar
jaafar has joined #ste||ar
hkaiser has joined #ste||ar
eschnett has joined #ste||ar
hkaiser has quit [Quit: bye]
hkaiser has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
rod_t has joined #ste||ar
zbyerly has joined #ste||ar
<zbyerly>
I have a question that might shock some people:
<zbyerly>
can I create an arbitrarily large number of localities on a single node?
<zbyerly>
or am I limited by the number of cores
david_pfander has quit [Ping timeout: 255 seconds]
EverYoung has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
<hkaiser>
zbyerly: you can create as many localities on a node as you wish, it will just run slow as hell
<hkaiser>
in general I'd suggest to make sure that the sum of all -tN for all localities on a node does not exceed the number of available cores
parsa has joined #ste||ar
aserio has quit [Read error: Connection reset by peer]
aserio has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
gedaj has quit [Quit: Leaving]
parsa has joined #ste||ar
Bibek has quit [Quit: Leaving]
Bibek has joined #ste||ar
aserio1 has joined #ste||ar
aserio has quit [Ping timeout: 240 seconds]
aserio1 is now known as aserio
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
EverYoung has quit [Ping timeout: 258 seconds]
hkaiser has quit [Quit: bye]
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
parsa has quit [Client Quit]
hkaiser has joined #ste||ar
<jbjnr>
hkaiser: here's a stupid question for you : the then_execute function is templated over the predecessor and Ts...&&args - but the .then only ever takes the predecessor as an argument. The Ts...args are never used. Are they there just for completeness - or is it allowed to say .then(future, more args) and add args to the continuation?
<hkaiser>
the args are there for symmetry with all the other executor API