Starts a non-blocking send of a buffer.
a0tError | a0ISendBuffer( | | | |
| | a0tPort | *port, | |
| | int | dest, | |
| | int | tag, | |
| | a0tRequest | *request, | |
| | a0tBuffer | *buffer );
| |
| Name | rd/wr | Description |
| port | read | Port to send to (on destination node). |
| dest | read | Destination node to send to. |
| tag | read | tag to use. |
| request | write | Request descriptor to hold the status. |
| buffer | read | Send buffer. |
This starts performs a non-blocking send to a given port port on a given node dest, with a given tag tag. It posts a request to send the buffer buffer.
The buffer cannot be modified before the completion of the request.
Only the amount of data packed in the buffer will be sent, regardless of the total size allocated. The buffer is kept intact after being sent. It can be sent again many times or be used to pack aditional data. To clear packed data inside a buffer and reuse it to pack new data, use a0ClearBuffer().
If a NULL is passed as request, no structures are kept after the request completion, so it cannot be tested or waited later. It is supposed that the program has other means to find out if the request has ended, as for example, a subsequent request.
On return of this function, the variable pointed by request contains an opaque request that can be used later to test or wait the completion status of the send operation.
| Error Code | Description |
A0Err...| Some error occurred. | |
A0ErrOk| Successful completion. | |
a0SendBuffer() a0Send() a0ISend() a0IReceiveBuffer() a0Pack() a0Unpack()