Changes between Version 13 and Version 14 of Aesop resource information

Timestamp:

01/18/12 11:00:43 (11 years ago)

Author:

carns

Comment:

--

Aesop resource information

@@ -38 +38 @@
 
 SSM makes progress on communication autonomously, even if you don't call wait().  So wait() does not drive communication progress, it only lets you find completion events.
+
+If the ssm_wait() function is sleeping in one thread, while another thread registers a callback and does a put/get, then the wait _will_ pick up the new completion event.  You don't have to restart the wait() call.  This simplifies the resource greatly.
 
 == Kevin's example of an SSM resource ==
@@ -95 +97 @@
 General issue: we need to discuss whether to keep wrappers for things like triton_mutex_lock().  If we do want to keep wrappers, we need to decide whether each component does its own wrappers or we all agree on a centralized implementation/wrapper across the project.
 
+= Future work (not enough time in this session) =
 
+Need to address semantics of ssm in relation to anl/triton work, independent of the resource implementation.  Let's pick back up on that this afternoon after completing the agenda.
+
+UAB can also send visitors to ANL easily if we need more interaction later.
+