Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
margo
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • sds
  • margo
  • Issues
  • #3

Closed
Open
Opened Dec 08, 2015 by Jonathan Jenkins@jenkins
  • Report abuse
  • New issue
Report abuse New issue

formalize relinquishing the thread to perform RPCs on

(Thought I'd give gitlab issues a try...)

Currently, the example creates and waits on an eventual for shutting down, in effect giving up the thread. The way it's set up, noone has access to the eventual though, so ctrl-c is the only option ;). It would be good to have formalized shutdown semantics so that the system can exit cleanly (e.g., when a database is closed). Not sure whether that would take the form of a shutdown RPC that sets the eventual (I've been using this method in my mercury examples for simplicity), or some other method (doesn't look like there are any "timed waits" in argobots). The function prototype for at least entering the loop could be something like int margo_listen(int seconds), where the return value is whether the instance has been told to shut down.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: sds/margo#3