Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
sds
margo
Commits
e52f73a6
Commit
e52f73a6
authored
Sep 07, 2017
by
Shane Snyder
Browse files
more readme edits
parent
a6087d81
Changes
1
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
e52f73a6
...
...
@@ -189,22 +189,21 @@ version 0.2:
* `margo_init()` is much more simplified and initializes Mercury and Argobots on behalf of
the user (with `margo_finalize()` finalizing them in that case)
* the prototype is `margo_init(addr_string, MARGO_CLIENT_MODE | MARGO_SERVER_MODE,
use_progress_thread, num_rpc_handler_threads)`
* the prototype is `margo_init(addr_string, MARGO_CLIENT_MODE | MARGO_SERVER_MODE, use_progress_thread, num_rpc_handler_threads)`
* `margo_init_pool()` is still available as an advanced initialize routine, where the
user must initialize Mercury/Argobots and pass in an `HG_Context` and `ABT_pools` for
RPC handlers and the progress loop
* Margo now has its own RPC registration functions that should be used for registering
RPCs (as Margo is now attaching internal state to RPCs)
* `MARGO_REGISTER` is basically equivalent to `MERCURY_REGISTER`, except it takes a
M
argo
instance
ID
rather than a Mercury class
`m
argo
_
instance
_id`
rather than a Mercury class
* `MARGO_REGISTER_MPLEX` is mostly the same as above, but allows a user to specify
an `ABT_pool` to use for a given RPC type
* relatedly, Margo users should now use `margo_register_data()` (rather than `HG_Register_data()`)
for associating user data with an RPC type
* like Mercury, there is a corresponding `margo_registered_data()` call to retrieve the user pointer
* the following Mercury-like functions are now defined within Margo, although it is
still safe to just use the Mercury calls directly (most are just #define
d
to the
still safe to just use the Mercury calls directly (most are just
`
#define
`s
to the
corresponding Mercury call, anyway):
* `margo_registered_disable_response()`
* `margo_addr_free()`
...
...
@@ -219,6 +218,6 @@ version 0.2:
* `margo_bulk_free()`
* `margo_bulk_deserialize()`
* `margo_hg_handle_get_instance()` and `margo_hg_info_get_instance()` calls have been added for
retrieving a
M
argo
instance
ID
given a received handle or the HG info struct associated
retrieving a
`m
argo
_
instance
_id`
given a received handle or the HG info struct
ure
associated
with the handle
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment