diff options
author | 2019-01-23 21:48:38 -0800 | |
---|---|---|
committer | 2019-02-05 18:07:43 -0500 | |
commit | f5a4a95f4dd8a09d28936c2e1e357e4c8dcca6c1 (patch) | |
tree | 92a19ff1facced603c1fd492b1f119168cb3c524 /include/rdma | |
parent | IB/hfi1: Build TID RDMA WRITE request (diff) | |
download | linux-f5a4a95f4dd8a09d28936c2e1e357e4c8dcca6c1.tar.gz linux-f5a4a95f4dd8a09d28936c2e1e357e4c8dcca6c1.tar.bz2 linux-f5a4a95f4dd8a09d28936c2e1e357e4c8dcca6c1.zip |
IB/hfi1: Allow for extra entries in QP's s_ack_queue
The TID RDMA WRITE protocol differs from normal IB RDMA WRITE
in that TID RDMA WRITE requests do require responses, not just
ACKs.
Therefore, TID RDMA WRITE requests need to be treated as RDMA
READ requests from the point of view of the QPs' s_ack_queue.
In other words, the QPs' need to allow for TID RDMA WRITE
requests to be stored in their s_ack_queue.
However, because the user does not know anything about the TID
RDMA capability and/or protocols, these extra entries in the
queue cannot be advertized to the user.
Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
Signed-off-by: Mitko Haralanov <mitko.haralanov@intel.com>
Signed-off-by: Kaike Wan <kaike.wan@intel.com>
Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'include/rdma')
0 files changed, 0 insertions, 0 deletions