1. Nov 04, 2019
  2. Jul 26, 2019
  3. Jun 27, 2019
  4. Jun 26, 2019
  5. Apr 24, 2019
  6. Apr 18, 2019
  7. Apr 17, 2019
  8. Apr 03, 2019
  9. Mar 08, 2019
  10. Mar 05, 2019
  11. Feb 21, 2019
  12. Feb 19, 2019
  13. Dec 19, 2018
  14. Dec 07, 2018
  15. Dec 05, 2018
  16. Nov 26, 2018
  17. Nov 12, 2018
  18. Nov 11, 2018
  19. Oct 31, 2018
    • Tommaso Tocci's avatar
    • Tommaso Tocci's avatar
      use mercury automatic SM routing · c40be81b
      Tommaso Tocci authored
      Mercury now support shared memory autorouting.
      
      A single margo instance can be initialized and it will handle both
      shared memory communication and remote ones.
      
      If the endpoint of the RPC is local mercury will automatically use
      shared memory.
      
      Since there is only one margo instance all the duplicated code for
      rpc/ipc have been unified and simplified considerably.
      
      ------
      
      The way in which client contact the server has changed.
      
       - Server initializes its own margo instance and generate the endpoint
      communication string using `HG_Addr_self`.
       - This endpoint description string is written on the pid file
       - When the client library loads it will fetch the server endpoint
      description from the pid file and will use that to contact the server.
      c40be81b
  20. Oct 29, 2018
  21. Oct 28, 2018
  22. May 02, 2018
  23. Apr 19, 2018
  24. Apr 12, 2018
  25. Mar 25, 2018
  26. Mar 20, 2018
  27. Mar 16, 2018
  28. Mar 14, 2018