John Biddiscombe
John Biddiscombe
You are correct - the bulk of the space is taken up by https://github.com/STEllAR-GROUP/hpx/blob/f341d96522ae2c6b55c42aef888e626b8bcb9b86/libs/full/runtime_distributed/src/big_boot_barrier.cpp#L96 the typenames registered.
I've replaced my existing code with a single new function defined in the base parcelport ``` // empty interface to allow libfabric parcelport to bootstrap virtual void pre_bootstrap_initialization() {} ```...
List of tasks has been updated/extended.
I asked about windows support on the libfabric mailing list and received the reply > Windows is supported. You should be able to run the networkdirect, tcp, sockets, and udp...
Just want to mention that the latest libfabric has early support for collectives https://ofiwg.github.io/libfabric/master/man/fi_collective.3.html this is one (more) reason why moving from a tcp (boost/std::asio) based default to a libfabric...
Note. I did not say it, but it is assumed that the receiving end of an rdma_action would receive a message that an rdma_operation had taken place and the reciving...
Note 2. The remote end of the action could also register actions to be triggered by index whenever an rdma operations take place, so that the fist rdma_action signature would...
That looks nicer (I like the second one, slightly more than the first, but I'm not sure why)
I've changed my mind, I like the first better.
further discussion on this topic from IRC might clarify some points. ``` heller 1) Why do you think we need to bypass serialization? What are your hopes there? What do...