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/
K-ballo has quit [Ping timeout: 244 seconds]
K-ballo has joined #ste||ar
K-ballo has quit [Ping timeout: 245 seconds]
K-ballo has joined #ste||ar
eschnett has joined #ste||ar
Yorlik has quit [Read error: Connection reset by peer]
K-ballo has quit [Quit: K-ballo]
eschnett has quit [Quit: eschnett]
Yorlik has joined #ste||ar
<Yorlik>
heller_: These Tony van Eeerd talks are really enlightening. I especially liked the example of these Berkley guys building an OS and having it explode after running for four years
<Yorlik>
The queue he presented made one thing pretty clear for me: The hard part seems to be (at least in my eyes), that lock free stuff it's not just difficult, but also especially hard to reason about - and how can you get something right if reasoning about it is already hard?
<Yorlik>
Maybe we need other thinking or language constructs to really think about it.
<Yorlik>
The acquire-release semantics seem to be a nice thing, but to me it looks as if this is just scratching the surface
<Yorlik>
The example of discussion in the C++ standard commitee about the correctness or non-correctness of not correctness of the code example with mixed acuire-release and relaxed semantics looked like a good example about how much we are still missing in properly understanding concurrency.
<Yorlik>
I'm trying to get my head around by thinking about concurrency in terms of contracts and expectations about data properties: What do I expect from a certain piece of data and what kind of contract exists (or does not exist)
K-ballo has joined #ste||ar
nikunj has quit [Ping timeout: 250 seconds]
nikunj has joined #ste||ar
hkaiser has joined #ste||ar
<jbjnr__>
hkaiser: yt?
<hkaiser>
jbjnr__: here
<jbjnr__>
quick question ...
<jbjnr__>
I've forgotten how the parelport bootstrapping happens. I wanted to get it running on the sockets libfabric for debugging thins ...
<jbjnr__>
after each node starts, it must send a message to the agas node
<jbjnr__>
but where and when does this happen.
<jbjnr__>
I init the agas_ locality on the agas node, but the other nodes need to connect to it and I can't remember where they call it from
<hkaiser>
jbjnr__: brb
<jbjnr__>
ok
<jbjnr__>
I think I know what to look for. I remember
<jbjnr__>
(maybe)
<hkaiser>
jbjnr__: that's in the bigbootbarrier code