Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
margo
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
12
Issues
12
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
sds
margo
Commits
6be169d8
Commit
6be169d8
authored
Mar 31, 2016
by
Philip Carns
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
explanation of examples
parent
0079d1ed
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
45 additions
and
0 deletions
+45
-0
README.md
README.md
+4
-0
README
examples/README
+41
-0
No files found.
README.md
View file @
6be169d8
...
...
@@ -21,3 +21,7 @@ Example configuration:
../configure --prefix=/home/pcarns/working/install \
PKG_CONFIG_PATH=/home/pcarns/working/install/lib/pkgconfig \
CFLAGS="-g -Wall"
## Running examples
See README file in the examples subdirectory.
examples/README
0 → 100644
View file @
6be169d8
This directory contains a collection of examples that can be run by hand.
They assume you are using a Mercury transport such as CCI or BMI that
understands the tcp:// address type. If you are using CCI then you probably
also want to run this fork of Mercury to allow the Mercury daemon to set its
own port at runtime:
https://github.com/carns/mercury
Assuming that you have met those requirements, then you can run the following
3 example scenarios with a server in one terminal and a client in another,
communicating via tcp over the localhost address.
----
A client issuing 4 concurrent RPCS, then a serial shutdown RPC, to a single
server that is using a dedicated execution stream to drive Mercury progress:
./server
./client
----
A client issuing 4 concurrent RPCS, then a serial shutdown RPC, to a single
server that is *not* using a dedicated execution stream to drive Mercury
progress. The server is purely single-threaded in this case:
./server single
./client
----
A client attempting to issue 4 concurrent RPCS, each with a 2 second timeout,
to a server that is deliberately hung in order to exercise Margo timeout
functionality:
./server-hang
./client-timeout
(this last test depends on Mercury functionality that is incomplete as of
this writing; it is not expected to complete)
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