1. Jan 29, 2020
  2. Nov 04, 2019
  3. Oct 03, 2019
  4. Sep 11, 2019
  5. Sep 05, 2019
  6. Aug 09, 2019
  7. Jul 26, 2019
  8. Jun 27, 2019
  9. Jun 26, 2019
  10. Apr 24, 2019
  11. Apr 18, 2019
  12. Apr 17, 2019
  13. Apr 03, 2019
  14. Mar 08, 2019
  15. Mar 05, 2019
  16. Feb 21, 2019
  17. Feb 19, 2019
  18. Dec 19, 2018
  19. Dec 07, 2018
  20. Dec 05, 2018
  21. Nov 26, 2018
  22. Nov 12, 2018
  23. Nov 11, 2018
  24. 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
  25. Oct 29, 2018
  26. Oct 28, 2018