Changes between Version 13 and Version 14 of Aesop resource information


Ignore:
Timestamp:
01/18/12 11:00:43 (11 years ago)
Author:
carns
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Aesop resource information

    v13 v14  
    3838 
    3939SSM 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. 
     40 
     41If 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. 
    4042 
    4143== Kevin's example of an SSM resource == 
     
    9597General 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. 
    9698 
     99= Future work (not enough time in this session) = 
    97100 
     101Need 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. 
     102 
     103UAB can also send visitors to ANL easily if we need more interaction later. 
     104