| 1 |
Nonblocking operations initiate a communication call and then return control |
| 2 |
to the application. The user who wishes to exploit nonblocking communication |
| 3 |
as a technique for latency hiding by overlapping communication with |
| 4 |
computation implicitly assumes that progress in communication can be made in a |
| 5 |
purely computational phase of the program execution when no communication |
| 6 |
calls are made. |
| 7 |
|
| 8 |
All the non-blocking transfer functions are prototyped to work as transfers |
| 9 |
with both "explicit" and "implicit handle". It stores important information |
| 10 |
about the initiated data transfer. The descriptor is implemented as an |
| 11 |
abstract data type. This is motivated by a simpler implementation so that a |
| 12 |
data transfer descriptor can be stored and managed in the application rather |
| 13 |
in the ARMCI library space. If a NULL value is passed to the argument |
| 14 |
representing a handle (thus representing "implicit handle"), the function |
| 15 |
does an implicit handle non-blocking transfer. A request data structure |
| 16 |
embedded in the handle should not be copied in the application. Upon |
| 17 |
completion of the data transfer, handle can be reused. A handle can be used |
| 18 |
to represent multiple operations of the same type (i.e., all puts or all |
| 19 |
gets). Such handle is an aggregate handle. Underneath, ARMCI combines multiple |
| 20 |
requests and processes them as a single message (actually by calling |
| 21 |
ARMCI_PutV/GetV/AccV). An explict handle should be initialized using the |
| 22 |
following macro, before it is used in any non-blocking operation. It is |
| 23 |
initialized as follows: |
| 24 |
|
| 25 |
- ARMCI_INIT_HANDLE(armci_hdl_t* nb_handle) |
| 26 |
|
| 27 |
Nonblocking operations in ARMCI allow user ot initiate a one-sided call and |
| 28 |
then return control to the user program. The data transfer is completed |
| 29 |
locally by calling a wait operation. Waiting on a nonblocking put operation |
| 30 |
assures was injected into the network and the user buffer can be now reused. |
| 31 |
|
| 32 |
Both in case of blocking and nonblocking store operations, to access the |
| 33 |
modified data safely from other nodes programmer has to call an ARMCI_Fence |
| 34 |
call first. ARMCI_Fence completes data transfers on the remote side. Unlike |
| 35 |
the blocking operation, the nonblocking operations are NOT ordered. |