| 1 |
|
| 2 |
DAPL Variations from IBM OS Access API |
| 3 |
-------------------------------------- |
| 4 |
|
| 5 |
The DAPL reference implementation is targetted at the IBM OS Access |
| 6 |
API (see doc/api/IBM_access_api.pdf). However, in the course of |
| 7 |
developing the reference implementation it has become necessary to |
| 8 |
alter or enhance this API specification in minor ways. This document |
| 9 |
describes the ways in which the Access API has been altered to |
| 10 |
accomodate the needs of the reference implementation. |
| 11 |
|
| 12 |
Note that this document is a work in progress/a place holder; it does |
| 13 |
not yet contain all of the API variations used by the reference |
| 14 |
implementation. It is intended that it will be brought up to date |
| 15 |
before the final release of the DAPL reference implementation. |
| 16 |
|
| 17 |
The variations from the IBM OS Access API are listed below. |
| 18 |
|
| 19 |
-- Thread safety |
| 20 |
|
| 21 |
The IBM OS Access API specifies: |
| 22 |
|
| 23 |
"Implementation of the Access APIs should ensure that multiple threads |
| 24 |
can call the APIs, provided they do not access the same InfiniBand |
| 25 |
entity (such as a queue pair or a completion queue)." |
| 26 |
|
| 27 |
This has been extended in two ways: |
| 28 |
* It is safe for multiple threads to call into the API |
| 29 |
accessing the same HCA. |
| 30 |
* Threads calling ib_post_send_req on a particular QP do not |
| 31 |
conflict with threads calling ib_post_rcv_req on the same |
| 32 |
QP. I.e. while there cannot be multiple threads in |
| 33 |
ib_post_send_req or ib_post_rcv_req on the same QP, there |
| 34 |
may be one thread in each routine simultaneously. |